> > The docs needs work. More to the point, complex things are complex. The > example you quoted to Matabele above is an attempt to build a fairly > complex little UI gadget and would be non-trivial in either JS or wikitext. > <javascript:> >
I very much agree. My pain point being that understanding and leveraging all this high-level syntax correctly appears to require unveiling a lot more concealed, under-the hood knowledge than a "trivial" js-script used to. Anyhow, I think I'll finally give it a shot, stop shying from plugin development and start fiddling with the basics <http://tiddlywiki.com/dev/#How%20to%20create%20plugins%20in%20the%20browser> to get the gist of it. In general, I have the impression that plugins... - mostly center around new widgets, extending widget functionality - perhaps js macros or macros simplifying widget use on top - stylesheet shadows to make it look right - language shadows for localization (, preferably dictonary tiddlers?) - configuration shadows (, also dictionary tiddlers?) Perhaps missing from the developer docs <http://tiddlywiki.com/dev>, what are the standards / recommendations for extending the system-tiddler namespace when it comes to plugin modules / components? Is the recommendation to simply put it all under *$:/plugins/githubuser/pluginname/*? Best wishes, Tobias. -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
