How linyi102/anime_trace works
Project type and purpose
• This is a cross‑platform Flutter application (“anime_trace”) that runs on Android, iOS, Windows and Web.
• Purpose: let users track anime watch history, take episode notes (with images), backup/restore data (locally or via WebDAV), and fetch metadata from online sources.
File structure
• Top‑level platform folders: android, ios, windows, web – hold native embedding, build scripts, platform channels.
• lib/ directory: the heart of the app, subdivided into:
• main.dart + global.dart – entry point and app‐wide initialization
• models/ – domain data classes (Anime, Episode, Note, Settings)
• controllers/ – state‑management logic using GetX (anime_display_controller, backup_service, theme_controller, etc.)
• dao/ – data access objects encapsulating SQLite operations (sqflite)
• repositories/ – higher‑level wrappers (e.g. bangumi_repository)
• utils/ – network clients (Dio), crawling modules for multiple anime websites, file and WebDAV utilities
• pages/ & modules/ & widgets/ & components/ – UI layer: screens, reusable widgets, dialogs
• routes/ – GetX route definitions
• values/ – constants, theme, assets
• Configuration files: pubspec.yaml (dependencies), Android/iOS/Windows build scripts, test/ folder with unit tests.
README for additional insights
• Confirms local SQLite storage + optional WebDAV backup
• Uses multiple third‑party packages (GetX for state, Dio for HTTP, sqflite for DB, webdav_client)
• Describes platform‑specific behaviors (Android only WebDAV backup, Windows local+WebDAV backup)
Detail
• Modules (e.g., note editor, crawling logic, backup service) as separate sub‑components
• That routes/get_route.dart connects navigation events to page widgets