> > Namespaces don't really mean anything for tiddlywiki at the moment aside > from this with names prefixed by $:/ are system tiddlers that don't show un > in normal searches and tiddlers prefixed by $:/temp/ or $:/state/ are > ignored when upgrading our importing tiddlers into a wiki. >
I think you should reconsider this statement and think outside the Jed-Box. At some point, people will mix and mingle contents and plugins and macros from different sources and then, all of a sudden, proper namespacing is the most crucial aspect for things to keep working! If a tiddler called Contacts is packed in a plugin it is still referenced > by [[Contacts]] unless you change the content of the tiddler, in which case > the modified one takes precidence, but deleting the modified version brings > back the original. Shipping a tiddler called "Contacts" with a plugin is a really bad idea, because there's a big chance that it's going to be overwritten or far too generic to be unique to whichever function you associate with it. > For this reason in many plugins the tiddlers in the plugin have > $:/plugin/(username)/(pluginname)/ added as a prefix to avoid naming > conflicts, but this is done by the plugin author and isn't required. So, yes... it is quite "required"... if we want to ensure interoperability. There is a whole range of design decisions and developing patterns that are a consequence of this very basic requirement, a "caption" field being just a basic example. 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.
