Descriptions like what PMario just included should be what one finds within the introductory developer documentation, that is currently lacking in useful examples and basic insights. Doing a Google search on most TiddlyWiki Widgets normally leads you to a Google Groups post and not to the formal documentation.
The documentation on Widgets <http://tiddlywiki.com/#Widgets>, for example, confusingly states, "Widgets are analogous to elements in an HTML document." *What?!?! * That sounds like widgets are simply nodes within an internally used DOM domain which *conceptually* are not what widgets are. My current understanding is that Widgets are better understood conceptually as *commands* within TiddlyWiki's own Domain-specific language <https://en.wikipedia.org/wiki/Domain-specific_language>. I'm not saying that these commands don't affect the browser's DOM or how tiddlers get rendered, but that *conceptually*, they are not the same thing. The Widgets <http://tiddlywiki.com/#Widgets> documentation even goes on further to confusing use the term "element widgets." But when you search for the term "*element*" at either tiddlywiki.com <http://tiddlywiki.com/#Widgets> or tiddlywiki.com/dev/ you will find no reference to the term used to explain what a Widget even is. Much of the documentation appears to be written from the perspective/context of being intended to be used solely as mental reminders to that same author that already possesses a comprehensive understanding of how TiddlyWiki functions internally. Personal perspective is not the best perspective/context in which to write documentation to an audience that doesn't share that same deep understanding. Personal mental reminders about a complicated subject are great for one's own personal use and consumption, but place huge barriers of entry to those new to TiddlyWiki development. Perhaps the developer documentation should add a *tiddlywiki.com/beginnerdev* documentation site that targets developers new to TiddlyWiki development. Thank you, -Doug On Thursday, February 16, 2017 at 3:55:34 PM UTC-6, PMario wrote: > > On Thursday, February 16, 2017 at 9:12:42 PM UTC+1, Mat wrote: >> >> >> IMO this phrase is not easily understood. I'm wondering if the following >> is a clearer (and accurate) description: >> >> The TiddlerWidget <http://tiddlywiki.com/#TiddlerWidget> sets a title to >>> be the regarded as current tiddler >>> <http://tiddlywiki.com/#Current%20Tiddler> within the scope of the >>> TiddlerWidget. >>> >> >> > I'm sorry, but this doesn't make more sense. At least not for me. IMO we > can't explain it on one sentence. > > currentTiddler is a *variable*, that is used by various core functions > and the UI, to show widgets, what's the current "scope" to work with. > > So functions like {{!!tags}} which is the same as: <$/transclusion > <http://tiddlywiki.com/#TranscludeWidget>field=tags/> know what's the > default tiddler to use, if there is no tiddler=xxx parameter. > > The list-widget would need to look like this: <$list filter="a b c" > variable=currentTiddler> ... scope ... </$list> everytime you use it. ... > This isn't convenient and very error prone. That's why there is a default > for many parameters, that widgets use. In the example, the list-widget > basically is a loop where currentTiddler is set to a, b and c > sequentially. > > The tiddler widget does the same thing, without the loop. It sets > currentTddler within the scope. > > <$tiddler tiddler=test> ... scope ... </$tiddler> > > That's it. > > -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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8a59a3ee-2602-4536-8f56-cf4aa1c9db6c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
