Plugins that define macros, views or other named entities are expected to prefix the name with their publisher identifier, for example: tiddlytools.slider.
<$juliankniephoff.frobnicate filter="[juliankniephoff.frobnicated[]] value=<<juliankniephoff.frob>> />
<$frobnicate twns="http://juliankniephoff.com/frobnicate">
Every named entity referred to in here is looked up in my plugin first
</$frobnicate>
<$jk:frobnicate twns:jk="http://juliankniephoff.com/frobnicate">
Every named entity referred to in here with a "jk:" prefix is looked up in my plugin first
</$jk:frobnicate>
Just out of curiosity: On this page about TiddlyWiki plugins I read the following:Plugins that define macros, views or other named entities are expected to prefix the name with their publisher identifier, for example: tiddlytools.slider.
However, I have yet to see a plugin follow this guideline. Is this still enforced/encouraged?
... should these be called $juliankniephoff.frobnicate, juliankniephoff.frob and juliankniephoff.frobnicated respectively?
(Of course none of this means anything. I'm just curious about the convention.)
> However, I have yet to see a plugin follow this guideline. Is this still enforced/encouraged?I think I wrote that right back in the beginning of TiddlyWiki5, when it was under development in 2011/12. Trying to learn from the experience of TW Classic, I was consciously trying to implement features that would help the community coalesce.As it's turned out, I don't think using the author prefix in the widget/macro name is a good approach, because of the inevitable wordiness it brings.
Tobias' idea of a central registry is not bad; if you're interested in setting it up, then I suggest that structuring the registry as tiddlers in the tw5.com wiki, but open to suggestions.
Tobias' idea of a central registry is not bad; if you're interested in setting it up, then I suggest that structuring the registry as tiddlers in the tw5.com wiki, but open to suggestions.
however definitely be part of the TW5 repo.
...
This should probably be accessible at:
I hereby nominate Tobias's excellent ` (backtick) macro and <<plugin-docs>> macro as the standard by which we should all wrote our plugin documentation to, and it should be part of the TW core so we can just include the right pluginname-info / pluginname-syntax etc. Tiddlers when we package up our plugins.