How emberedsky/skydl works
a. User Interface Layer:
• Elements such as App.xaml, MainWindow.xaml, and HelpWindow.xaml. These define the UI and interaction side.
b. Application / Business Logic Layer:
• Core logic coded in files such as App.xaml.cs, MainWindow.xaml.cs, and HelpWindow.xaml.cs. Although all are in the solution root, these contain the code-behind that orchestrates the program’s behavior.
• This layer as the “Controller” handling inputs from the UI, managing workflows, and coordinating tasks.
c. External Dependencies / Services:
• That the business logic layer interacts with these tools by executing them (likely via command-line calls or process execution commands).
d. Configuration and Project Settings:
• Although less prominent in functionality, include your configuration files such as App.config and build/deployment artifacts (Skydl.csproj, Skydl.sln, packages.config). They represent setup and dependency management.
e. File System & Data Storage:
• Where downloaded or processed files are stored. A component representing file I/O or a “File Manager” module can be added to show data output and logging (for example, Msg to Empy.txt or similar artifacts).
Relationships and Interactions
• The UI layer sends user commands (download, convert, trim, etc.) to the Business Logic/Controller.
• The Controller then processes these actions by invoking the appropriate external services (youtube-dl, ffmpeg, AtomicParsley).
• Incoming data from the UI into the Business Logic.
• Outgoing commands from the Business Logic to each external dependency.
• Data flow from external tools (such as downloaded media or conversion output) back to the application for display or saving to disk.
• That some operations might require piping results between tools (e.g., trimming using ffmpeg on a file initially downloaded by youtube-dl).
Architectural Patterns and Design Principles
• External Process Invocation: Since core functionalities are delegated to external programs (youtube-dl, ffmpeg, etc.), show how the application acts as an orchestrator.
• Decoupled and Modular Design: Emphasize that each external dependency is treated as a separate component that could be updated independently (e.g., updating youtube-dl without affecting the main application logic).