> > Once we all have a Tiddlywiki to share we would 'join' them together. > > This joining would create an independent Tiddlywiki to call Tiddlers > > based on Tags using the loadTiddlers with tag option you could pull > > all of the data that is tagged 'public' as an example.
That's the idea behind using: http://www.TiddlyTools.com/#LoadTiddlersPlugin You can create sets of externalized tiddlers, stored in other TW documents, and then embed one or more <<loadTiddlers tag:something ... temporary>> somewhere on the page to automatically import them. If you save remote TW documents using either http://www.TiddlyTools.com/#ExportTiddlersPlugin or http://www.TiddlyTools.com/#SaveAsPlugin you can quicly write either full TW documents or reduced-size "PureStore" format documents, containing selected tiddler data. PureStore files omit the TW core code (saving about 350K per file), making it easy to create and share small online 'distribution-only' tiddler repositories into which people export only those tiddlers that they actually want to publish. If you also install http://www.TiddlyTools.com/#TemporaryTiddlersPlugin you can use <<loadTiddlers>> to auto-tag the imported tiddlers with "temporary" so they *won't be saved* when you save your own document, so that only your own tiddlers are actually stored locally. If you want to keep the imported tiddlers in your local document (for offline reading, perhaps), simply remove the 'temporary' tag (or disable/uninstall the plugin) and those tiddlers will be saved normally. Of course, each time you reload, these locally-stored, imported tiddlers will again be retrieved from the remote document, so you will always be viewing the latest published revisions. If you make changes to a *local* copy of an imported tiddler, you can tag it with "noReload" so that it won't be overwritten with the latest *remote* version when you reload your document. A more typical use- case might be to actually rename the modified local copy, so that the remote copy is still automatically imported, without overwriting the local tiddler content. You can then use http://www.TiddlyTools.com/#CompareTiddlersPlugin to determine the exact differences between the locally-stored tiddler and the freshly-imported remote tiddler. You might also want to consider using something like: http://www.TiddlyTools.com/#ExternalTiddlersPlugin This plugin extends the TW core <<tiddler>> macro to permit use of *external file or URL references* in place of the usual TiddlerName, so that content can be automatically transcluded from a remote source. The enhanced refernce syntax also support use of a fallback mechanism so that you can list *multiple* potential sources for the transcluded content. Each source is attempted in turn, until one is successful and the content is rendered. There are, of course, numerous other ways that these plugins could be combined to implement a variety of info-sharing scenarios for small/ medium sized groups. I'm sure you'll think of some! enjoy, -e Eric Shulman TiddlyTools / ELS Design Studios -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
