| Age | Commit message (Collapse) | Author |
|---|
|
* [refactor] moving main.setPath listener outside start method
* [refactor] setpath tells if game path is set or not
* newpath event tells if game path dialog is successful or not
* [feat] main window will not show if path is not set
* [feat] viper displays a dialog and exits if no game path was prompted
* [fix] viper prompts for game path if viper.json:gamepath is not set
* [feat] translating gui.gamepath.must key
* code cleanup
fixing single quotes and alike
* fix gui.gamepath.must message
Co-authored-by: 0neGal <mail@0negal.com>
|
|
* [chore] adding electron-updater dependency
* [feat] adding auto-updating mechanism
* [chore] setting package version to v0.8.0
* [fix] restoring original repo URL
* [docs] adding some documentation about publishing new releases
* [chore] adding publish:windows command
* [docs] updating publish instructions with new publish command
* [chore] adding publish:linux command
* [docs] updating publish instructions
* --updatevp, and option to disable auto updates
If you want you can set "autoupdates" to false in your config, no GUI
tools to do this yet. For the CLI auto updates is off by default and
you'll have to use --updatevp.
I also removed the snap package, tho whether this stays as a change is
still to be discussed.
And with the new option I updated the help menu, the man page and
everything along else that needs it.
* removed "soon" parts of README for auto-updates
* [feat] adding French translation for cli.help.updatevp key
* confirmation for restarting the app
Now instead of automatically updating and restarting the app, which may
be slightly confusing to some users, (the app opens then closes and then
opens), it now asks whether you want to restart and open the new
version. If you say no, instead next time you launch it, it'll be on the
new version.
If you want to completely disable updates you can disable it in the
viper.json file...
* [feat] adding French translation for gui.update.available key
* added configuration instruction in README
Co-authored-by: 0neGal <mail@0negal.com>
|
|
|
|
The buttons in the GUI disable whilst you're updating Northstar and
potentionally doing other things in the future, I also added a way to
log things in the app, albeit it just prints it in the "Welcome to
Viper!" part of the app, which is just fine.
I also added all the needed language strings for the GUI logs and
removed "gui.missinggamepath" as we use it for both the CLI and GUI even
tho "general.missinggamepath" exists, and so we now use the general one
for both, as the messages are the same.
|
|
|
|
The version now refreshes when you update/install Northstar, I renamed
vpVersion/nsVersion to just vpversion/nsversion and
getInstalledVersion() to getNSVersion(), removed uses of
getElementById() with just the ID. I also added English localization.
The versions text color is now bound by a CSS variable (we may use it in
the future again).
I'm also not sure what the point of `style="white-space: nowrap;"` was,
as I don't see much of a difference? Rather instead use `<nobr>` in the
lang file if needed.
Besides that I did tiny code cleanup.
|
|
feat: Icons
|
|
Simply code style changes, also removed the content of the version divs
since they'll be replaced anyway.
|
|
into feat/icon
|
|
|
|
|
|
|
|
Apparently I'm dumb and when I did this I read what it was on by default
when making the `width` variable, when doing so I accidentally read the
height's value (115), compared to the width (600), I don't know how I
managed to do this, I'm dumb...
|
|
This should more or less ensure everything remains responsive even if
the language is one with very long strings.
|
|
|
|
|
|
|
|
|
|
|
|
This means devtools don't get opened no matter what and --debug is
required for it to open.
|
|
I removed the titlebar, which I already had gone on my Linux system,
besides that I also made it so the body of Viper can be held down to
drag it around. And then added an exit button.
|
|
I haven't tested this on Windows... And I will in a bit...
|
|
I think?
|
|
Everything is now in utils.js and simply gets called through IPC calls
which make it quite simple to add CLI arguments...
|
|
|
|
|
|
|
