This introduces interface components for Thunderstore mods listing.

• Displays information about mod
• Thunderstore mod page can be opened in default browser via information button
• Mods can be searched through (filtering by mod name / author / mod description)

TODOs

• [x] Responsive layout
• [x] Pagination (displaying all mods is slow on some devices) (THAT'S FOR ANOTHER TIME)
• [x] Search debounce (not to trigger search at each character input)
• [x] "Install/Installed" button text
• [x] Actual mod installation
• [x] Blur background on this view
• [x] Update view once a mod has been installed
• [x] Display "updating" instead of "installing"

For now simply parses enabledmods.json. Note that this file will not be up-to-date if the user just installed a mod but hasn't launched Northstar yet.

Instead of using solely enabledmods.json parse the mod.json of found mods in mods folder.

Use the mod.jsons to get list of mods and compare with enabledmods.json to set which mods are enabled.

With EA switching from Origin to EA App, we need to check for that instead.

Resolves an issue where EA App users are unable to launch Origin cause "Origin is not running".

Longterm, we should just launch via Steam and/or EA App directly, passing -norhtstar in the process to get it to launch Northstar instead.

This is the basic code needed to install a mod from Thunderstore.

There's an issue where the removal of the temporary download folder does not work properly which I have yet to resolve.

• [x] Basic install logic
• [x] Prevent installing Northstar or NorthstarReleaseCandidate
• [x] Handle dependencies -> Waiting on libthermite update as current is broken.
• [x] Add Thunderstore dependency string to mod.json (for checking for updates).

In a discussion in voice-chat with Emma and Spoon we concluded that switching to Northstar RC release channel should be more accessible without activating DevView.

The goal is to strike a balance between easier to switch to release candidates while also being hard enough to deter someone from accidentally or unknowingly enable it and keeping it enabled.

A suggested idea was having a checkbox to enable "Playtester mode" that then in turns allows switching release channel in PlayView using a dropdown menu or similar.

Hidden behind dev view. Helps with testing as dev builds of Northstar do not update patch number so an update check bypassing button is necessary to launch dev builds of Northstar.

Display Northstar release notes in application.

TODOs

• [x] Scrollbar
• [x] Keep menu visible when scrolling
• [x] Dates style (use dark theme?)
• [x] Display a loader while fetching notes
• [x] Ensure HTTP call is not done on main thread

Allows deleting a Northstar mod from within FlightCore

• [x] Requires #109
• [x] https://github.com/R2NorthstarTools/FlightCore/pull/110#pullrequestreview-1224588360 (81f5e7373bc399c646ff29c0fb8a3c647e2f56c4)

The unwraps would cause the thread to crash in case FlightCore is unable to use Powershell output to find Origin Titanfall2 install path. Instead we just return the error message which is caught and handled by the parent function.

Helps with differentiating which window is which when both developing FlightCore and is using release version at the same time. Wouldn't be the first time I accidentally nearly confused the two :P

Rendered result:

We pass some data from backend to frontend via custom objects/structs (whatever they are called). For typing to work in TypeScript we need to also define an interface for that object in TypeScript.

Keeping the Rust<->TypeScript object definition synced manually is annoying and prone to errors. Instead we should auto-generate them from the Rust code where applicable (usually the definition in Rust is the "main" one) so that any changes in the Rust object get automatically transferred to the frontend.

A Tauri macro complains when the dist folder does not exist. Adding a .gitkeep means that cloning the repo, the folder will be created.

Talking about this macro error

Note that the macro error does not prevent compilation in any way. It's purely an annoyance thing :P

When installing a mod with a dependency that requires an older version of said dependency than what is already installed, we should show a warning and/or option not to downgrade.

:warning: This is a draft PR to showcase the potential of having variable number of entries in the tab bar. :warning:

Idea:

By default only show base tabs but offer various buttons to open other views. Once opened this views will stay available on the tab bar until the end of the session (i.e. until the application is restarted).

Advantages:

• Switching between views is instant. E.g. switching from Thunderstore mod install to launching game is just 2 clicks (switch to PlayView, click on launch game). This is quicker compared to e.g. Viper where browsing mods opens a pop-up overlay.
• No overwhelming new users by not showing all views "immediately"
• No need for any subpages/subviews. Just add another tab :P
• As usually not all tabs will be opened in one session, the tab bar will stay small in general.
• Anything else?

Disadvantages:

• If buttons to open hidden views are not well placed, users might never discover them
• Variable number of tab entries bad? (I don't see the issue personally but I might just be missing sth ^^)
• Anything else?

Rendered:

https://user-images.githubusercontent.com/40122905/209241721-3d81ef59-8c5f-4ed8-9ce8-1c50d461548b.mp4

Important note: The views to hide by default were chosen to be the ones that I deemed to be used less often. This does not mean we should actually hide these specific views by default on main. This was just for the sake of the demo. For example Thunderstore view is way too pretty to hide it :P

Hmm, for that we need to signal core mods from backend to front-end. I don't think we have something for that yet... :/

Originally posted by @GeckoEidechse in https://github.com/R2NorthstarTools/FlightCore/pull/110#discussion_r1054898148