mirror of
https://github.com/kuhyx/diet-guard.git
synced 2026-11-21 05:12:18 +01:00
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>
57 lines
2.2 KiB
Dart
57 lines
2.2 KiB
Dart
/// Picks a photo and copies it into permanent app-local storage.
|
|
library;
|
|
|
|
import 'package:diet_guard_app/services/blob_store.dart';
|
|
import 'package:diet_guard_app/services/blob_store_factory.dart';
|
|
import 'package:flutter/foundation.dart';
|
|
import 'package:image_picker/image_picker.dart';
|
|
import 'package:path/path.dart' as p;
|
|
|
|
/// Wraps [ImagePicker] and persists the result in a [BlobStore], so the
|
|
/// returned key survives after the picker's own (possibly cache-cleared)
|
|
/// temp file is gone.
|
|
///
|
|
/// Photos are device-local only: per the sync plan (Milestone 3), a logged
|
|
/// entry's `imagePath` is stripped before push and never read from a pulled
|
|
/// remote copy, so nothing here needs to be sync-aware. That also means a
|
|
/// photo attached on the desktop is never visible on the phone, and vice
|
|
/// versa -- by design, not by omission.
|
|
class PhotoAttachService {
|
|
PhotoAttachService._(this._store);
|
|
|
|
static PhotoAttachService _instance = PhotoAttachService._(null);
|
|
|
|
/// The singleton instance.
|
|
static PhotoAttachService get instance => _instance;
|
|
|
|
BlobStore? _store;
|
|
|
|
/// Redirects where picked photos are stored, so a test never touches the
|
|
/// real store. Pass null to restore default behavior.
|
|
@visibleForTesting
|
|
static void resetForTesting({BlobStore? store}) {
|
|
_instance = PhotoAttachService._(store);
|
|
}
|
|
|
|
Future<BlobStore> _resolveStore() async => _store ??= await openBlobStore();
|
|
|
|
/// Opens [source] (camera or gallery) and stores the picked image.
|
|
///
|
|
/// Returns the new blob key -- an absolute path on Android, an IndexedDB
|
|
/// key in the browser -- or null if the user cancelled the picker.
|
|
Future<String?> pickAndStore(ImageSource source) async {
|
|
final picked = await ImagePicker().pickImage(source: source);
|
|
if (picked == null) return null;
|
|
final store = await _resolveStore();
|
|
// `readAsBytes` rather than a file copy: the browser's picker hands back
|
|
// a blob URL with no filesystem behind it.
|
|
return store.put(p.extension(picked.path), await picked.readAsBytes());
|
|
}
|
|
|
|
/// Returns the bytes stored under [key], or null when the photo is gone.
|
|
///
|
|
/// Backs the web image widget, which cannot render from a path.
|
|
Future<Uint8List?> readBytes(String key) async =>
|
|
(await _resolveStore()).get(key);
|
|
}
|