User settings library

[jesus2099]

Let's try GM_config instead of my own!

---

Now that I know that libraries are fun to use and work OK. I could start using a common USER-SETTINGS library of the same kind as the user settings I provide for SUPER TURBO but better.

Some people (CatCat) prefer having lots of small scripts while some other may prefer having less scripts. Some other people suggested merging same purpose scripts together (an inline info display script, an edit review script, a (mass) editor script, etc.). Having the possibility of same user setting system in all scripts would allow splitting/merging SUPER TURBO and other scripts into more comprehensive, homogeneous and/or simple unitary scripts (to be determined).

Ideas in no special order :

• [ ] Script codename, display name (optional and optionally localised), description (optional and optionally localised) and link (optional)
• [ ] Make it easy to understand and use by other script authors ?
• [ ] Find a cool (yet acceptable for others) name (like MB USER SCRIPT SETTINGS ?)
• [ ] Category and sub‐category
• [ ] More types than just simple text fields and check‐boxes
• [ ] Use it in SUPER TURBO
• [ ] Use it in mb_ALL-LINKS to kill two birds with one stone (#61, #61-protect-user-customised-ALL-LINKS branch ← IMPORTANT)
• [ ] Use it panel‐less (API’s set) fashion in mb_INLINE-STUFF (hide/show ISRC/AcoustID, edit inline track≠recording display pattern, etc.)
• [ ] API would provide, for each setting, set, reset (to default), undo (one level) and would provide the same kind of user setting panel than found in SUPER TURBO. It would be one panel per script or a global panel (with tabs or something)

[yvanzo]

What about using GM_config?

[jesus2099]

Thanks @y-van-z, I’ll have a look at it. At first sight, their demo does not seem to work in my browser.

[jesus2099]

FTR it seems one has to install the script before seeing the demo (sizzlemctwizzle/GM_config#64).

[Martii]

Fixed.

[jesus2099]

It looks great, thanks @Martii. :)