Mario and Coda, Thanks for the feedback. - I wonder how these alternates stand against my suggestion of hackability through patchability <https://groups.google.com/forum/?hl=en#!topic/tiddlywikidev/-aC6jWNTHdI> . - Please note for the "action on any button" I propose does not demand any differentiation between pre/main and post actions. It is simply used as a trigger. - Can you explain further when and how one would want to differentiation between pre/main and post actions
On refactoring to handle pre, body and post actions - I must say I acknowledge this depreciation of action widgets in the button widget body. - I do not understand the technical reason for this and have expressed my dissatisfaction with this because it stops buttons and their actions being able to be a self contained piece of code, but I also see now it will be difficult to do a number of things we can do now. - You can see this even more when you want to apply conditional actions inside the button, or additional actions or if you are trying to apply actions inside a list to operate on sets of tiddlers. - Imagine if we were no longer permitted to code action widgets inside buttons how would we address my design, your suggested pre and post actions, conditional and bulk actions? - The idea that buttons can only be designed to work by reference to external definitions of macros/variables containing the actions is to me retrograde at least for the average user. I stand to be corrected but it seems to me deprecating actions widgets inside buttons is causing more problems than advantages and solves a "problem" not visible to most users and designers. When this happens in other aspects of my life, *when the cure is worse than the disease*, my usual strategy is to return to the original problem and revisit it to see if there is an alternate way to address it. Perhaps the system code can be refactored to address any perceived technical issues while retaining the current outwards functionality. The problem is because I do not understand the problem this is supposed to solve I can't try and find a solution. You are both already talking about fundamental changes to the button widget so it seems revisiting this is almost necessary anyway. Perhaps another strategy would be to build a new widget, perhaps action-button that has the additional subtlety encoded. Perhaps designed from the ground up so that it works equally well with actions inside the button widgets, so this need not be deprecated. I know you are both quite capable of creative thinking, and deep knowledge, so I would hope you can give this suggestion a little more thought. Thanks heaps Tony On Wednesday, October 2, 2019 at 5:12:28 AM UTC+10, coda coder wrote: > > > > On Tuesday, October 1, 2019 at 12:25:21 PM UTC-5, PMario wrote: >> >> >> - pre-actions and >> - post-actions >> >> >> > Thanks Mario. I had similar thoughts but couldn't find a way to express > them. Notionally, in my head I had something like this: > > <$pre-actions> > <$button ...> > <$post-actions> > > which is obviously unworkable. But now I'm seeing: > > <$button preactions=<<pre-actions>> actions=<<my-actions>> postactions=< > <post-actions>> ...> > > > I also like this, but I don't know if it's feasible: > > \define my-button-pre-actions() ... > \define my-button-actions() ... > \define my-button-post-actions() ... > > <$button data-id="my-button" ...> > > > > > -- 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/542543d2-5155-40a6-a8f9-e38c0686099b%40googlegroups.com.
