weegeekps / open-dcs-launcher Goto Github PK

The module management window is an important piece of this, and figuring out the design is essential. We need to design the window and then create the view.

The window will need to:

• Parse a file containing metadata for all of the potential modules.
• Generate widgets based on the metadata provided.
• Allow users to install, reinstall, or remove modules.
• Allow users to quickly open Kneeboard folders for the modules.

There is a drop down at the top of the Main window where the user can choose which DCS installation they want to use. We need to implement this.

Version 0.1.0 will only have two options in this menu: Stable and Beta. Future versions may support more than two installations. However, because we need to support the multi-threaded version of DCS in the beta branch, we should also include that in the selections as well.

Ended up adding localization to the Settings WIndow. Should do the same for the Main Window.

Depends on #7.

Once we have a design for the Module Management window, we need to implement the underlying functionality to actually perform the install, reinstall, and remove actions.

Need documentation for usage.

• Basic installation instructions
• Usage instructions

The DCS updater has both a repair action and a cleanup action that should be made available in the launcher.

The branch selection should not be null after saving settings. Despite resetting it to the first item, it's not updating. Probably some WinUI 3 quirk.

This would be nice to have for 0.1.0 but not essential.

Need to write up a contributors guide before release. This should explain the GPL licensing for newcomers, how to develop within the project, and the style and coding guide.

WinUI 3 supports custom title bars. This would be a nice feature to use, especially for dark mode.

When the application starts up, we need to get the user's settings from local storage and parse them, or prompt them if no settings file exists.

• Prompt for Settings on Start.
• Deserialize on Start.

Apparently WPF was very much the wrong choice. I can save a lot of my XAML designs, but this project should to migrate to WinUI 3.

• Rename existing main branch to main-old.
• Create new main branch.
• Migrate code.
• Delete main-old branch.

The early styling is done for the Settings window, but we need to implement functionality.

Implement:

• Browse Buttons.
• Serializing settings to TOML file. This file should be stored in local storage.
• Validation that the paths are correct.

We need a CI environment that runs code style checks, unit tests, and creates installer artifacts.

There are two buttons that correspond to launching either DCS or the DCS Updater in the Main window. The functionality for each is similar so we can implement them together. They should launch DCS.exe and DCS_updater.exe respectively. Additionally, if the multi-threaded option is chosen in the selector, DCS.exe in the bin-mt folder should be used instead.