Bimlas I am happy to illustrate the value in adding additional actions to core buttons. I am writing now as I sit in a hospital waiting room. The two general approaches are to intervene at appropriate times and add features while simplifying interaction. The proposed solution is designed to be extended with multiple solutions being able to add actions without overwritting other additional actions.
An example I used as a test was any action on every button was recorded in a log of actions. This is a way to track activity to create an audit trail or potentially add an undo feature. An action on tiddler done, close and cancel can stop a timer and log elapsed time. An action on edit could throw a dialogue if no current user is set. An action on save wiki could store the last modified date and user. Any button could record its use in a data tiddler e.g. theme switch and permit an undo. A project tiddler could set the current project then revert to the previous one on close. Open in new window button could set an indicator in the main window. An additional dialogue could be generated on encrypting a tiddler advising the password be recorded. The close all button could trigger a save wiki and prompt for a new user name. Closing a specific tiddler could trigger a custom actiin like disable a plugin. Using the settings icon could trigger a warning message or backup current settings. New here could also set a parent field The home button could open default tiddlers plus a specific tiddler based on other values. And many more.... -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/5bdbaf8a-7675-4127-8a0f-e31dc7600609%40googlegroups.com.
