How natanmiuz/nonet works
Project Type and Purpose
• This is a standalone, desktop-centric Python application bundled into an .exe (via PyInstaller or similar).
• Purpose: Provide a GUI tool (“NONET”) for downloading video/audio from platforms (YouTube, Facebook, TikTok, Twitter), leveraging FFmpeg for processing and platform-specific downloader logic.
File Structure Analysis
• Top-level
• main.py → entry point
• requirements.txt → Python dependencies
• dist/NOTNET.exe → packaged executable
• app/ → core application package
• app/
• core/downloader.py → download logic, platform detection
• utils/helpers.py → shared utility functions
• utils/styles.py → UI styling constants
• views/main_window.py → GUI definition (window, controls, callbacks)
• External binary requirement: FFmpeg (to be placed under binaries/ per README)
• README emphasizes using FFmpeg, no other services are hosted locally.
Key Architectural Components
a. User Interface Layer
• main_window.py: input fields, buttons, progress bar, notifications
b. Application Logic Layer
• core/downloader.py: URL parsing, platform auto-detection, download orchestration
c. Utility Layer
• helpers.py: path management, URL validation
• styles.py: theming and styling constants
d. External Dependencies
• FFmpeg binary (binaries/ffmpeg.exe) for media conversion
• Platform APIs / Python libraries (youtube-dl or pytube) specified in requirements.txt
e. Packaging Layer
• PyInstaller (implied) for producing dist/NOTNET.exe
Relationships and Data Flows
• User action → GUI (main_window)
• GUI invokes Downloader API → Downloader core logic
• Downloader uses Helpers for I/O, platform detection
• Downloader triggers external library calls (YouTube/Facebook/TikTok/Twitter)
• Media streams piped through FFmpeg for format/quality conversion
• Converted file saved to disk → Downloader notifies GUI
• GUI displays success/error notification
Important Architectural Patterns
• MVC-like separation: Views (GUI) ↔ Controller (event handlers in main_window) ↔ Model (Downloader core logic)
• Layered architecture: UI → Business Logic → Utilities → External Services
• Single executable deployment (monolith) for portability