| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
|
|
|
|
|
|
This isn't present in the current release and is a bug that crept up
with the upcoming release, however of course, it's been fixed now.
|
|
|
|
|
|
This makes opening and closing popups a little bit easier, on top of it,
it also fixes a bug where you could open the settings popup on top of
the browser popup or other popups, and it'd hide the background blur,
but still show both popups.
|
|
|
|
Very useful stuff!
|
|
The amount of times I've broken something with `backdrop-filter` is far
too many, but what can you expect.
|
|
I will likely add more buttons in the future, but for now this is most
of the ones a user could need to repair problems.
|
|
Most of these are from back when Viper was originally started, I also
removed a few keys as they were no longer in use, but were forgotten
about, most of these are from pre-v1.0.0 aka, the old smaller UI
|
|
The `lang()` function doesn't change whatsoever, as the lang files are
flattened and are therefore identical to the before this commit.
I also cleaned up the files, and all the lang files should now all look
far more similar in order.
|
|
|
|
|
|
They're pretty simple to use, and automatically make themselves fit on
screen, on top of automatically disappearing and appearing of course.
I've used them a few places now, and not sure where else they can be
used, there are of course localization strings that need, well,
localization, and I'll create a PR for this on a later date.
|
|
I also made mods with updates be placed in the top of the modlist.
|
|
When a red switch is placed besides a red button that says "Remove", it
makes it seem far more destructive to click that switch, even if it's
not, and a blue color doesn't fit in very well either (perhaps we need
more colors). And so because of all that the modlist switches are now
orange, and we can easily add more colors.
The switch colors overall are also far more vibrant now, as it looks far
better that way.
|
|
The new modlist now uses the same toggles found in the settings popup,
only here they're used to disable/enable mods. On top of this I also
fixed the "Toggle All" button not working. Forgot to change some stuff,
breaking it... oops...
|
|
Previously some outdated packages would just say "Re-Install" and not
"Update", now that's fixed, along with making the logic easier for use
in the mod list.
|
|
The current design for the installed mods is not exactly the best. And
it has been due for a redesign for quite a while, I'm finally starting
work on this.
|
|
|
|
Some functions have been renamed:
update() -> updateNorthstar()
updatevp() -> updateViper()
Overall these are far better function names...
|
|
Only on the titles, putting them only on the options or on both the
title and options would be far too much, just the title is perfect.
|
|
|
|
This doesn't fully implement everything as the master server is down
whilst making this commit, so I can't fully implement it.
|
|
"Info" -> "View", along with a button in the previewer to open the mod
page in the browser if you so choose.
|
|
Instead of opening your normal web browser you can now just open the
page inside Viper, many changes aren't finished yet, notably the
webview.css file.
At some point I'll split the main.css into more files so the folder
makes sense even though there's currently only one file in there.
|
|
sped up some animations, added a few more colors to different places,
overall just a slight spice up to the UI
|
|
This is for the sake of UX, as a user might be confused about why it
doesn't work as they may not notice that they've to turn off auto-detect
language first.
Because of this Settings.switch() now has a state value, and if you
provide a DOM element as the element arg it now uses that to know what
to toggle, before we used to just provide a number, which made sense for
generating the onclick events, but not for this task...
This whole thing was brought up because of #115
|
|
This allows someone to have their system in any language, and then have
Viper in a separate language. This is also useful for testing.
|
|
For testing purposes I had the mod browser auto show on startup, that's
removed now, I also when refactoring some code forgot to change the name
of a function everywhere, leading to an error.
|
|
Fully implemented (I think? Maybe there's an edge case?), albeit it's
missing "Updateable" and "Installed" filters, but they'll be added later
|
|
I localized all strings for English, then went ahead and made array
options have a wider input and more word spacing, since they're all
space separated.
|
|
It actually saves settings, loads them properly and everything...
|
|
Albeit only frontend functionality, it doesn't actually save your
settings, it simply loads them, and Settings.get(), allows you to
convert them to a format that can be used to save settings.
|
|
I added descriptions and options for excluding files.
|
|
This only has the actual UI for the settings page in place, no actual
functionality has been implemented yet. I made several changes not
directly related to the settings page, such as changes the CSS color
variables to use RGB, as to easily add an alpha channel to colors. I
also changed the way the Browser is toggled in some respects and many
other changes that makes it easy to re-use the browser code to create
the settings UI
|
|
Since apparently dragleave and dragenter don't quite work as intended we
have to resort to this obscure method which should work just fine on the
user's end.
|
|
No functional toasts yet, just the code for them, I'll add the actual
toasts later...
|
|
This should fix the window drag not working, however I cannot test that.
As my WM doesn't support it, a Windows contributor will have to test it.
I also added an info button that opens the mod's page in your web
browser, this button is of course localized, along with that I localized
the placeholder in the search input.
There's also a few general aesthetic changes, like adding a tiny border
around #modsdiv and #browser.
|
|
|
