mirror of
https://github.com/kuhyx/diet-guard.git
synced 2026-11-11 17:13:58 +01:00
Krzysztof kuhy Rudnicki
802ee0fe6d
Flutter's Linux embedder manages ~20fps at 3840x2160 -- measured on a stock `flutter create` counter app, so it is the toolkit rather than this code -- where the same Dart rendered by Chrome sustains ~144fps (evidence in ~/todo/docs/desktop-performance-findings.md). The desktop target therefore becomes a Flutter *web* build; Android is untouched. `dart:io` does not fail a web *compile* -- it resolves to a stub that throws at runtime -- so every platform edge moves behind a conditional export rather than being discovered later as a blank white window: - storage: `document_store*.dart`, files on Android and IndexedDB in the browser (mirrored to the desktop wrapper, which is what makes a wiped Chrome profile recoverable). Document names stay the exact pre-web filenames so an installed phone keeps reading its existing log. - photos: `blob_store*.dart` plus `attached_image*.dart`, since `Image.file` cannot resolve an IndexedDB key. The picker itself has web support; what changed is the storage and display model. Camera *capture* is genuinely lost on desktop -- and photos never crossed devices anyway, `imagePath` being stripped before push. - scheduling: `background_tasks*.dart`. A browser has no WorkManager equivalent -- a closed tab runs nothing -- so the desktop runs an in-page 5-minute check while its window is open. That loses nothing on the PC, where `diet-guard-gate.timer` already locks the screen on an unlogged slot, which is strictly stronger than a notification. - notifications: `notification_backend*.dart`, the browser Notifications API in place of flutter_local_notifications. - the GitHub token: `token_vault*.dart`. On web it is *not* held by the browser at all -- flutter_secure_storage's web backend is WebCrypto-wrapped localStorage with the wrap key beside the ciphertext, which is obfuscation, not encryption at rest -- so the desktop wrapper owns it and proxies the API (`github_client_factory*.dart`). `Platform.isAndroid` itself throws on web, so every platform branch now tests `kIsWeb` first; the battery-optimization row (permission_handler, no web implementation) is hidden off Android. The desktop pushes under device id `desktop`, not `phone`: sharing an id would have made the two devices overwrite each other's pushed log on every tick. The Python side enumerates device directories generically, so it needs no change. Tests move onto the same seams -- the file-backed stores keep the atomicity and unreadable-file guarantees where they belong. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
76 lines
2.8 KiB
Dart
76 lines
2.8 KiB
Dart
/// Shows/cancels the per-slot "meal not logged" notification, mirroring
|
|
/// diet_guard's `_gate.py` lock decision -- but as a notification rather
|
|
/// than a screen-grab, and re-evaluated on every background check tick
|
|
/// rather than fired once.
|
|
library;
|
|
|
|
import 'package:diet_guard_app/models/slot.dart';
|
|
import 'package:diet_guard_app/services/notification_backend.dart';
|
|
import 'package:diet_guard_app/services/notification_backend_factory.dart';
|
|
import 'package:flutter/foundation.dart';
|
|
|
|
/// Owns the due-slot notification logic ([syncToSlots]) independently of the
|
|
/// platform surface that actually posts them: `flutter_local_notifications`
|
|
/// on Android, the browser's Notifications API in the desktop web build (see
|
|
/// `notification_backend.dart`).
|
|
class NotificationService {
|
|
NotificationService._(this._backend);
|
|
|
|
static NotificationService? _instance;
|
|
|
|
final NotificationBackend _backend;
|
|
|
|
bool _initialized = false;
|
|
|
|
/// Returns the initialized singleton; throws if [init] was not called.
|
|
static NotificationService get instance => _instance!;
|
|
|
|
/// Initializes the singleton with the platform backend (idempotent -- a
|
|
/// second call returns the already-initialized instance without
|
|
/// re-running platform setup).
|
|
static Future<NotificationService> init() async {
|
|
final svc = _instance ??= NotificationService._(openNotificationBackend());
|
|
if (!svc._initialized) {
|
|
await svc._backend.initialize();
|
|
svc._initialized = true;
|
|
}
|
|
return svc;
|
|
}
|
|
|
|
/// Resets the singleton so tests can inject a backend -- typically one over
|
|
/// a plugin pointed at a fake platform channel. A subsequent [init] call
|
|
/// drives that backend's `initialize` codepath, same as production.
|
|
@visibleForTesting
|
|
static void resetForTesting({NotificationBackend? backend}) {
|
|
_instance = backend == null ? null : NotificationService._(backend);
|
|
}
|
|
|
|
/// Requests the platform's notification permission.
|
|
///
|
|
/// Returns null where the concept doesn't apply; callers treat null and
|
|
/// false the same way.
|
|
Future<bool?> requestPermission() => _backend.requestPermission();
|
|
|
|
/// Shows a notification for every slot in [dueSlots] and cancels one for
|
|
/// every other known slot.
|
|
///
|
|
/// Idempotent and re-evaluated every tick: a slot logged after its
|
|
/// notification fired gets that notification cancelled on the very next
|
|
/// call, mirroring `_gate.gate_is_due()`'s re-evaluate-every-tick
|
|
/// behavior rather than firing once and forgetting.
|
|
Future<void> syncToSlots(List<int> dueSlots) async {
|
|
final due = dueSlots.toSet();
|
|
for (final slot in daySlots()) {
|
|
if (due.contains(slot)) {
|
|
await _backend.show(
|
|
slot,
|
|
'Meal not logged',
|
|
"You haven't logged your ${slotLabel(slot)} meal yet.",
|
|
);
|
|
} else {
|
|
await _backend.cancel(slot);
|
|
}
|
|
}
|
|
}
|
|
}
|