| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Previously packages were filtered based on whether
Browser.filters.get().filtered included any of the categories, now
however it only checks if one of 4 filters is selected, Skins, Mods,
Client-side and Server-side, anything beyond that like "Language: EN" is
ignored and unless it doesn't have any of the other filters selected
it'll go unfiltered.
Previously when selecting every filter you'd still only get 100'ish
packages at best, now you get the full 150 that there currently is on
Thunderstore, except for r2modman and Northstar itself.
|
|
If the only results when searching are elements that are filtered then
it just infinitely shows loading instead showing "No results..."
|
|
|
|
|
|
|
|
Clicking the filters button would close then reopen it, instead of
closing, then opening when clicking again.
|
|
This is easier to manage, and a lot less annoying to navigate, having to
scroll through many lines of code is annoying, categorizing makes it
easier, I also overall improved the layout of many of the CSS files.
|
|
It now contains info about `build/publish.sh`
|
|
feat: Better Browser
|
|
Add missing French translations to better-browser
|
|
|
|
Better browser "es" localization
|
|
#125
|
|
This was just so I didn't have to go to the Mods tab, click "Find Mods",
and click "View" on one of the mods.
|
|
Instead of instantly flashing when it's done loading and so on, it now
fades in, instead, without any problems.
|
|
"Info" -> "View", along with a button in the previewer to open the mod
page in the browser if you so choose.
|
|
It now looks a lot better overall. Still missing a few things, like
showing when it's loading, but besides that it's pretty much done.
|
|
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.
|
|
Instead of setting the innerHTML every single time an element get added
it now just appends them like you should be doing, but I was lazy when I
wrote the original code I guess.
Not only does this improve performance, but it also fixes the CSS fade
animation not making every mod element/entry flicker, and instead now it
only does it on the new ones, like intended.
|
|
In the past when more than 50 packages was loaded it'd simply display a
"Maximum packages loaded" message, and it wasn't actually 50, as it just
took the first 50 packages loaded, whether or not they were filtered
out, so now that's fixed and a "Load more..." button has been added.
With that comes some changes to the lang strings for
"gui.browser.endoflist" and a new one "gui.browser.loadmore".
I also fixed the filtered packages issue also occurring in searches.
This will overall allow a user to more easily find the maximum amount of
packages without loading literally over a hundred packages at once, not
good for performance...
|
|
Made the UI slightly bigger, and the mod elements aren't on their own
line, this allows you to see more at once while it being bigger and more
telligble, before it was kind of empty.
|
|
feat: Dependency support
|
|
|
|
If you already have all the dependencies or some dependencies of a
package those will be skipped, if there is no dependencies missing it'll
just install, and otherwise it'll show the missing and ask whether you
want to install them.
Meaning if a package has two dependencies and you've one of them only
the one you don't have will show up.
|
|
"gui.mods.confirmdependencies" "es" localization
|
|
#122
|
|
This should allow you to install packages that have dependencies,
however maybe not with the best UI/UX experience, as currently there's
only an English localization, and we also install dependencies even if
the dependency is already installed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Instead of updating the branch it was easier to simply add this, I don't
plan to add the issue/PR support, as it's complicated with no real
benefit, as NS seems to already link the PR's themselves.
|
|
Simplifies the parsing of Markdown, whilst also solving problems that
the previous parser for Markdown caused.
|
|
Bump ejs from 3.0.2 to 3.1.7
|
|
Bumps [ejs](https://github.com/mde/ejs) from 3.0.2 to 3.1.7.
- [Release notes](https://github.com/mde/ejs/releases)
- [Changelog](https://github.com/mde/ejs/blob/main/CHANGELOG.md)
- [Commits](https://github.com/mde/ejs/compare/v3.0.2...v3.1.7)
---
updated-dependencies:
- dependency-name: ejs
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Implement enabledmods.json
|
|
The GitHub projects page is never updated, and it never will be, so I've
removed it's link and replaced it with something useful.
|
|
|
|
Due to me being bad at touching the computer I messed up here.
|
|
Everything seems to be working just fine, and I can't find any problems,
so I'll likely merge this soon.
|
|
Instead of repeating code and everything, get() now only returns a
boolean, based on the arg inputted into get(mod), it returns true if the
mod is enabled and false if disabled.
If the mod isn't found inside the enabledmods.json it is assumed that
it's enabled, as Northstar doesn't update this unless you actually
disable the mod first, and the mod won't be found in there.
Then I used get() to simplify list() a whole lot, and adding that
functionality of using the manifest for a version number if one couldn't
be found in the mod.json.
|
|
|
|
Albeit mods.list() doesn't actually search the manifest file for a
version number, and I'll implement that later.
|
|
|
|
This was meant to be used for the reset config prompt, but confirm()
doesn't allow you to change the button messages, which I forgot when I
was making this lang string, and subsequently lead to me forgetting I
even made the string, accidentally pushing it...
|
|
Essentially just validates the config file and then prompts you about
it, it allows you to reset it directly or just to exit and let yourself
fix it. And because the error message appears directly in the renderer
we have access to navigator.language, and can therefore still localize
the string. However! We can't actually care if the user has disabled
auto detection of their language, since... y'know, the config file where
that's stored isn't able to be read properly.
And so I added an argument to lang(), which allows you to force it to
use a specific language if that language is available, if not it
defaults back to English.
|
|
|
