How voice-less/whatsapp-msgstore-viewer works
Project Type and Purpose
• A desktop cross-platform (Linux/Windows/Mac) Python application with a Kivy/KivyMD GUI.
• Its core functions are to decrypt (via an embedded Crypt14/Crypt15 decrypter), read, and display WhatsApp SQLite databases (msgstore.db, optional wa.db) and linked media.
High-Level File-Structure Analysis
• MVC layers:
– View/ (all .kv files, screen classes under View/*)
– Controller/ (screen controllers chat_screen.py, login_screen.py, etc.)
– Model/ (one model per screen)
• Data access: dbs/abstract_db.py plus versioned schemas in dbs/v1/db.py.
• Decryption: decryption/dbs/WhatsAppCrypt14Crypt15Decrypter subtree wrapping ElDavoo’s CLI library.
• Utilities: Utility/Utils.py, Utility/observer.py implementing common helpers & observer pattern.
• Assets: fonts, images under assets/.
• Entry point: main.py.
A. Frontend (UI)
• Kivy App (main.py) launching a ScreenManager.
• Screens: LoginScreen, MainScreen, ChatScreen, TemplateScreen.
• UI Widgets & Components (custom .kv files under View/components/).
B. Controllers
• One controller per screen in Controller/*.py.
• Bridge between View and Model, handles user events.
C. Models & Business Logic
• Screen-specific Model classes in Model/*.py.
• Data aggregation, formatting for UI.
D. Data Layer
• dbs package:
– AbstractDatabase interface (abstract_db.py).
– Concrete schemas (dbs/v1/db.py).
• Decryption subsystem:
– Python wrapper (decryption/dbs/.../decrypt14_15.py)
– Java utilities under utils/ within that folder.
E. External & OS Resources
• WhatsApp DB file(s) on disk (msgstore.db, msgstore.db.cryptX, wa.db).
• Local media directory.
• Third-party libs: Kivy/KivyMD, SQLite, external decrypter.
Relationships & Data Flows
• User clicks UI element → Controller receives event → Controller invokes Model method →
Model calls either:
– Decryption module (if DB encrypted) → yields decrypted DB file
– DB schema loader (dbs) → queries SQLite → returns raw data
→ Model formats into viewable objects → Controller passes to View → View renders.
• Utility/observer.py may broadcast changes (e.g., DB loaded) to interested components.
• Assets (images/fonts) are referenced by the View at runtime.
Architectural Patterns & Principles
• MVC (Model-View-Controller) clear separation.
• Plugin-style schema loading (dynamic discovery of dbs/v* packages).
• Observer pattern (Utility/observer.py) for decoupled event propagation.
Essential Details to Capture
• Entry point (main.py) and app initialization.
• ScreenManager switching among screens.
• One-to-one mapping of Controller ↔ Model ↔ View screens.
• Observer utility broadcasting DB-loaded or schema-added events.
• Assets directory feeding media previews.