Hi Tony, I think your POC is very well thought out! ... I do see some inconsistencies, but most of them are inherited from the core.
The inconsistencies come from the ongoing development of the <$button> widget, late adding of "actions" parameter and adding the <$action-xxx> widgets. So I think, the first step would need to be, that we "clean" the existing core/ui/buttons/xxx from the message-parameter. This parameter can be replaced by defining the button "actions" parameter using action-widgets. The same thing can happen with <$action-xx> widgets in the button-body. They can also be moved to the "actions" macro. Which also has some advantages. eg: <<now>> macro is re-calculated on button click and not on button rendering. ... As I wrote at the GitHub issue <https://github.com/Jermolene/TiddlyWiki5/issues/4272#issuecomment-534493531>, we have several action "insertion points". Every single one of them can be a valid usecase for different type of users. With the core, we need to be as open _and_ generic as possible. This can lead to more complexity as we want. With all actions in the "actions-macro" definition, there are only 2 insertion points left. ... - pre-actions and - post-actions This mechanism makes everything predictable and much simpler as 4 possible insertion points. ... BUT ... It also means that we need to rewrite the existing core buttons and make them "predictable" ... AND ... 100% backwards compatible. Compatibility _may_ be hard part here. just some thoughts. mario -- 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/4c5cb95d-3482-4817-88fb-ef00c69bb2d6%40googlegroups.com.
