Lists the authors of projects on the Manage Modules Window. If a url is provided in the module.json file, it will make the version tag link to the module url.
Currently, the šbutton pops up a text list of which modules will be enabled by confirming the dialog. This doesn't expose any but the most recent saved state, however, and could be improved upon. My rough-sketch suggestion for how to design the dialog:
[list button] being a button to produce what we currently get, i.e. the text list of enabled modules,
[enable-this button] selecting that particular module set to load immediately,
[Restore button] would be the same as clicking the enable button on the first line,
and cancel is self-explanatory.
depending on UI complexity goals, another options would be to not have individual enable buttons per line, but instead have the line desired be selectable somehow (some sort of whole-line click, or just a radio/exclusive checkbox column), and have the Restore button be the sole trigger for actually Doing the Thing.
One consideration is what to do with, for example, saved states 1-3, if one were to jump back to state 4. Since the current UI wouldn't let you get back to 4 without going through 1-3, deleting as you go, I see no problem with just discarding them.
Currently, the šbutton pops up a text list of which modules will be enabled by confirming the dialog. This doesn't expose any but the most recent saved state, however, and could be improved upon. My rough-sketch suggestion for how to design the dialog:
[list button]being a button to produce what we currently get, i.e. the text list of enabled modules,[enable-this button]selecting that particular module set to load immediately,[Restore button]would be the same as clicking the enable button on the first line, and cancel is self-explanatory.depending on UI complexity goals, another options would be to not have individual enable buttons per line, but instead have the line desired be selectable somehow (some sort of whole-line click, or just a radio/exclusive checkbox column), and have the
Restorebutton be the sole trigger for actually Doing the Thing.One consideration is what to do with, for example, saved states 1-3, if one were to jump back to state 4. Since the current UI wouldn't let you get back to 4 without going through 1-3, deleting as you go, I see no problem with just discarding them.