| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
This is achieved by sending an IPC event to the renderer and waiting for a reply once
Since this is async we return from the function after sending the event and recursively invoke it once the reply arrives
The package data is returned a a JSON String because Electron is unable to copy the Object over IPC
|
|
|
|
|
|
|
|
|
|
https://github.com/0neGal/viper/pull/241
|
|
|
|
|
|
|
|
feat: Linux launch support v2
|
|
This will be particularly useful for #239
|
|
This will be particularly useful for #239
|
|
|
|
|
|
|
|
Too busy with the frontend, and forgor to change the main process IPC
event listeners, whoopsie.
|
|
Technically this is also broken on the main branch, however it's a lot
easier to just fix here, instead of having to fix it there, then also
fix it here, due to the modularization
|
|
|
|
|
|
|
|
And `js/popups.js`, but it was already technically a CommonJS module, it
was just leftover in `index.html` due to `js/browser.js` not being a
CommonJS module.
|
|
It's not actually used anywhere outside of itself, but oh well.
|
|
|
|
|
|
Renamed from `toast.js` to `toasts.js` as well
|
|
|
|
|
|
Far from done, but this pretty much splits everything inside
`src/app/main.js` into separate files.
|
|
|
|
|
|
|
|
Spelling corrections
|
|
|
|
Pesky EA Desktop being annoying as always, leaving behind processes, to be
fair, I don't exactly think you're supposed to be killing it it like
this, but oh well, it seems to function now.
|
|
This didn't happen in all cases, so it took me until randomly
discovering it recently, for me to actually realize there was a problem,
and then subsequently fixing it.
|
|
Did an oopsie whoopsie doopsie, now its unoopsied
|
|
|
|
|
|
|
|
|
|
|
|
The "Steam (Auto)" launch method should ideally work in all scenarios,
ideally! Obviously, I can't and haven't tested in every environment, but
I've attempted to make sure it functions.
Launching Vanilla and Northstar works just fine, custom launch arguments
also work just fine, it works with normal Steam, Flatpak Steam, and as a
fallback with the Steam Browser Protocol (`steam://`)
There's also the option to set your own/custom launch command for both
the Vanilla and Northstar launch options. How well they work will of
course depend on what the user set them to.
"Steam (Auto)" attempts to pick the right Steam launch method depending
on what's available, if the Steam executable can be found, it'll use
"Steam (Executable)", if it cant and Flatpak is found on top of an
install of Steam through Flatpak, then "Steam (Flatpak)" is used, if all
of that fails, then we attempt to use "Steam (Protocol)"
Some toasts will be shown if you attempt to run the game with either
"Steam (Executable)" or "Steam (Flatpak)" and they cant find the
game/Steam. This isn't an issue with "Steam (Auto)"
|
|
|
|
Previously, settings using `<select>`'s for their value only worked on
the `forcedlang` setting, now it just works overall, this wasn't an
issue before, as we had no need for it.
More importantly `forcedlang` is special in that it dynamically loads
the list of languages available, so it was and still is handled
separately, to support that behavior.
|
|
It's not capable of formatting language files, and now has a prompt
interface for editing and adding missing localization strings.
This removes the need for manually editing localization files beyond
`en.json`, it'll still be edited manually. But maintainers will no
longer have to open any localization files.
I also updated the documentation for contributing to localizations.
|
