HI Pat, when you are writing a widget which response to some event, it is possible to cause other events. Action events (at present) are children - so the control passes in the direction away from the root of the widget tree, conversely messages travel in the other direction, toward the root, and are caught by a widget that is listening for that type of message. I talk a little about it here: https://groups.google.com/forum/#!searchin/tiddlywikidev/design/tiddlywikidev/et0wVg-J6Gw/TjAdeVUhyGMJ
cheers BJ On Saturday, March 7, 2015 at 12:21:01 PM UTC-6, PE Pat wrote: > > Hi all, > > As I learn more about TW, I am coming into more contact with its core > structure, but I still don't really understand it. What is the difference > between action widgets and messages, in terms of how they are handled and > how they can be used? > > My usecase: a unit planner app, which is essentially a program that > manages a bunch of different lists. Currently, I have action widgets called > <$append> and <$remove> which add or remove a tiddler/tiddlers to lists in > other tiddlers, but I am starting to think that those might be more > appropriately implemented as messages. > > Here's why: I see that I can dispatch a message within the Javascript code > of a widget, but I don't know if I can call a widget from inside another > widget (or if that even makes sense in TW). So I guess my specific question > is: does it make more sense to define common list operations as messages so > that they can be dispatched as necessary in other, more complicated widgets? > > Thanks, > Pat > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
