Folks
I love this abstract thinking and do it a lot myself.
Keep in mind the same "method" can be applied to more than one tiddler. To me
macros and buttons can do this and in some ways transcluding a special tiddler
(like an object) via the view template conditionally can apply a method to a
tiddler.
My recent use of storyTiddler allows you to coopt current tiddler as a
parameter to a "method" e.g.
{{Param||methodtiddler}} in wich current tiddler becomes Params tiddler has the
login and the real current tiddler is in storyTiddler variable. You can access
all fields on the storytiddler, or the param tiddler and with and additional
variable the methodtiddlers fields.
One coding practice of mine is to avoid the use of the text field on working
tiddlers to reserve it for notes so I have to use the view template to display
tiddler content.
Of interest with method tiddlers that have wiki text code in them you can
define macros, introduce styles, wiki text and widgets in a single tiddler.
I am currently researching code patterns to ensure this approach is
comprehensive and without gaps.
One gap I am working on is automating the setting some fields based on a value
in a variable for widgets that only accept fields or text references. To do
this I need to use the open tiddler trigger.
Another endeavour of mine is to make use of existing triggers usually in
existing buttons to trigger additional actions to reduce the need for
additional triggers the user needs to pull. I am somewhat slowed down on this
because its similar but different to Jeremy s project to allow widgets to have
custom actions.
Regards
Tony
--
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/25dbd247-8e62-463d-9f7a-d8a486cfe7bb%40googlegroups.com.
