Moved the manageModCategory function call to the end within prepareModsTab. This ensures that category management happens after resolving the UI elements, maintaining the logical sequence of operations.
Renamed the `view` method to `type` in parserAthShield.js to better reflect its purpose. Removed unused `athShield` import from landing.js and added it to settings.js. Added a manageModCategory function in settings.js to manage the display and interaction state of the Mods tab based on the type of `athShield`.
* First step to use Language .json file in ejs
* i18n for landing.ejs
* i18n for login.ejs
* i18n for loginOptions.ejs
* i18n for overlay.ejs
* i18n for settings.ejs
* i18n for waiting.ejs
* i18n for welcome.ejs
* langloader.js placeholder support
* i18n for landing.js
* i18n for login.js
* i18n for overlay.js
* i18n for settings.js
* i18n for uibinder.js
* i18n for uicore.js
* remove html language replacement
* use toml for i18n
* Fix mojang/microsoft status icon is undefined
* cascadable langloader
* separate lang file for customization
* move some placeholder text to _placeholder.toml
* Update
* Reduce package lock diff.
* Remove another placeholder.
* Checkbox does not require translation.
* Icons don't need translation.
* Leave placeholders inline.
* Fix translation for news pages.
* Remove more unneeded translations.
---------
Co-authored-by: Daniel Scalzi <d_scalzi@yahoo.com>
* Patches to get 1.17 working, need to revise into real solutions.
* Add version.jar to cp until 1.17.
* Add server selection button to Java settings tab in preparation for by-instance java settings.
* Java settings by instance
* Use classpath flag instead of hardcode.
* Support 1.19.
* Fix refresh of java exec details.
* Add doc.
* Fix auto download of jdk 17.
* Dependency upgrade.
* Update landing.js
This changes the Skin/Avatar server displayed on the landing page to one that displays the hat layer which then features the skin correctly.
* Create landing.js
This changes the Skin/Avatar server displayed on the landing page to one that displays the hat layer which then features the skin correctly.
* Updated remaining Crafatar URLS
Changed Crafatar URLS to matching mc-heads url.
Vendor name is now displayed above the selected Java version on the settings page. This is to allow for easier differentiation between versions (ex. Amazon Corretto vs AdoptOpenJDK).
Fixed file selectors not behaving properly due to breaking change in Electron 7 (#67).
Renamed shell.openItem to shell.openPath (Electron 9 breaking change).
Resolves#67.
Removed commonDirectory.
Removed instanceDirectory.
Added dataDirectory. The common and instance directories are now resolved from this.
The config.json and distribution.json are now stored in Electron's data folder (app.getPath('userData')).
Users can edit the dataDirectory under launcher settings.
Added saving function, add pack button, drag and drop functionality to the button, ability to
refresh the list of packs.
Added height limit to the dropdown with scrolling. Cleaned up some styles.
You can now drag one or more files onto the add mods button in order to add them to the mods directory. Only jar, litemod, and zip files will be moved.
Changed eslint to use a single configuration file, with overrides for the UI scripts.
Now using fs-extra, replace usages of rimraf and mkdirp with fs-extra functions.
If the instance mods directory does not exist when the 'Add Drop-In Mod' button is clicked, it will be created.
The update selected server code has been modified. Previously, the server would be updated before the mod config was saved. This has been fixed so that the mod config is saved before the server is switched.
Updated electron to v3.0.10.
The AutoUpdater requires that macOS builds be code signed. That is currently not possible.
As a workaround, the autoupdater on mac will now alert users that an update is available and give the option to download the file directly from GitHub.
Closes#16.
Added a settings tab to manage updates.
On this tab you can:
* Init auto update check.
* View update information (version, prerelease vs release, etc).
* View update changelog.
* Install updates (when downloaded).
The green glow on the landing page now takes users to the settings tab. Updates can be installed from there.
This UI can be changed in the future if needed.
Mod configurations can now be changed and saved.
Still pending optimization to allow required mods to
properly declare optional mods.
Show main UI on interactive event. We shouldn't wait for
remote images to load first.
Removed the version from the module's name. The version can be retrieved
from the identifier and placed wherever desired.
Reorganized the modules to have the more popular/important mods listed
first. The order in which modules are declared is the order they appear
on the UI.
Updated the docs to make it clear that maven identifiers are required for
all modules not of type File.
Linted the entire project. Using different rules for the script files
as there are a lot of undefined variables just because of the way the
DOM's global scope works.
Mostly just code cleanup, however the linter did catch a minor bug with
a settings regex. That has been corrected.
Added distromanager.js to represent distro elements.
Moved all distro refresh code to distromanager.js.
Overhauled assetexec.js.
Overhauled handling of assetexec.js output in landing.js.
Overhauled events emitted by assetguard.js.
Improved doenload processing in assetguard.
Updated discord-rpc to v3.0.0.
Replaced westeroscraft.json with distribution.json.
Use npm in travis for windows + linux.
Remove file extension from imports.
Added liteloader + macromod + shaders to distribution.json.
If the value of a ranged slider is out of range, the slider will snap to either 0% or 100%.
Reduced memory label margin to preserve sufficient spacing.
The left side of the settings UI now has a more comprehensive layout.
Settings tabs now scroll all the way to the frame bar. When the content is scrolled out of view, a drop shadow is displayed. This removes the awkward feel of content scrolling into nothing.
This tab displays information about the current version of the application. Release notes are fetched from GitHub's atom feed and displayed here as well.
