| Age | Commit message (Collapse) | Author |
|---|
|
This should more or less ensure everything remains responsive even if
the language is one with very long strings.
|
|
|
|
This may or may not be how we actually do localization in the future,
however for now this seems doable. I will obviously need to look at how
we detect the language, as I think instead of relying on names like
"en-US" just have "en", so we don't have to symlink various editions of
English to the same file. But for now this is a draft, and the important
part of this is rather how the underlying localization works.
|
|
We now just use a fixed string ("viper.json")
|
|
However, I can't figure out a way to directly exclude it in the unzip
package, hence, it just renames the original to "<file>.excluded" when
the extraction is done it then renames it back to it's original aka
"<file>", overwriting what was extracted, which essentially excludes
some files.
If there exists an unzip library/package that has options for excluding
files we should move to that, but until something as such is found the
current way is how we'll do it.
|
|
This uses your system appearance to figure out which one to use. Meaning
the people with dark mode enabled on Windows or through their GTK/QT
theme will still see dark mode...
|
|
This means systems (like most Windows installs) that don't have the font
can still be allowed to see it in all it's glory.
|
|
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.
|
|
Im a dumbass and made a tiny mistake...
|
|
I haven't tested this on Windows... And I will in a bit...
|
|
|
|
Everything is now in utils.js and simply gets called through IPC calls
which make it quite simple to add CLI arguments...
|
|
|
|
|
|
|
|
|
