Viper - Launcher+Updater for TF|2 Northstar

about summary refs log tree commit diff

path: root/src/app/settings.js

Age	Commit message (Collapse)	Author
2023-01-27	move app/*.js files into app/js/	0neGal

2022-05-30	refactored event names	0neGal
	Quite a lot of them aren't in the same syntax/style, and it's quite bad to look at, this should fix them all without causing issues.
2022-05-30	fixed missing commas and various syntax stuff	0neGal
	I know, commas aren't needed, however, going in and out of using commas and not using them also looks bad, so generally I try to always use them, with exceptions.
2022-04-17	changing the language now disables autolang	0neGal
	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
2022-04-13	the user can now manually select a language	0neGal
	This allows someone to have their system in any language, and then have Viper in a separate language. This is also useful for testing.
2022-02-24	fixed NS never being auto-updated and more	0neGal
	When #87 was merged an unnoticed problem slipped in where if Viper was running in a version that did not support auto-updates we would never auto-update Northstar. Now that's fixed, and the nsupdate option is completely implemented. I also took the liberty of removing the auto-update option in the settings page if Viper can't auto-update anyway, as it's useless if that's not possible.
2022-02-23	settings page is now fully functional	0neGal
	It actually saves settings, loads them properly and everything...
2022-02-21	some functionality is now present	0neGal
	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.
2022-02-20	initial work on settings page	0neGal
	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