mirror of
https://github.com/kuhyx/diet-guard.git
synced 2026-11-11 19:53:53 +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>
55 lines
1.9 KiB
Dart
55 lines
1.9 KiB
Dart
/// In-page scheduling for the browser-hosted desktop app.
|
|
///
|
|
/// A browser has no equivalent of WorkManager: a closed tab runs nothing, so
|
|
/// the due-slot check can only run while the desktop window is open. That is
|
|
/// an accepted, deliberate reduction rather than an oversight -- on the PC the
|
|
/// real backstop is `diet-guard-gate.timer`, which *locks the screen* on an
|
|
/// unlogged slot and is strictly stronger than any notification this app could
|
|
/// raise.
|
|
library;
|
|
|
|
import 'dart:async';
|
|
|
|
import 'package:diet_guard_app/services/due_slot_check.dart';
|
|
|
|
/// How often the in-page check re-evaluates due slots.
|
|
///
|
|
/// Five minutes rather than WorkManager's 15: a foreground timer is cheap,
|
|
/// and the window is usually open for a short session, so a long period would
|
|
/// often mean the check never runs at all.
|
|
const inPageCheckInterval = Duration(minutes: 5);
|
|
|
|
Timer? _timer;
|
|
|
|
/// Starts the in-page periodic due-slot check (idempotent).
|
|
///
|
|
/// Runs one check immediately so opening the window is itself a check, then
|
|
/// repeats every [inPageCheckInterval] for as long as the page lives.
|
|
Future<void> initBackgroundTasks() async {
|
|
if (_timer != null) return;
|
|
_timer = Timer.periodic(inPageCheckInterval, (_) => _runCheck());
|
|
await _runCheck();
|
|
}
|
|
|
|
/// No-op on web: there is no out-of-page scheduler to hand a retry to.
|
|
///
|
|
/// A push that fails while the window is open is retried by the next
|
|
/// foreground sync; one that fails as the window closes is picked up on the
|
|
/// next launch.
|
|
Future<void> enqueueSyncBackstop() async {}
|
|
|
|
/// Cancels the in-page timer. Exposed so a test can stop the periodic work it
|
|
/// started rather than leaking it into the next test.
|
|
void stopBackgroundTasks() {
|
|
_timer?.cancel();
|
|
_timer = null;
|
|
}
|
|
|
|
Future<void> _runCheck() async {
|
|
try {
|
|
await checkAndNotify();
|
|
} on Exception {
|
|
// A failed check must never take the app down: the next tick retries.
|
|
}
|
|
}
|