Hi Tobias > 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.
Yes, except that the "concealed, under-the-hood knowledge" is just poor documentation. 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/*? > Yes, that's the best practice. It isn't enforced as a restriction because there are some situations where a plugin needs to define a shadow tiddler outside its namespace. For example, the core plugin defines "GettingStarted", "$:/ControlPanel" etc. as shadow tiddlers. Other plugins may want to provide defaults (eg visibility of toolbar buttons that they include). Best wishes Jeremy. > > Best wishes, Tobias. > -- Jeremy Ruston mailto:[email protected] -- 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.
