I'm working on a proof-of-concept TiddlyWiki demonstrating the value of this platform as a learning tool for information architects. TiddlyWikis are well-suited organizational systems, provide a rich variety of labeling and navigational systems, and excel at content search and recall. The two features I will focus on are the separation of content from presentation and content reuse. Through color palettes and theme switchers it will be easy to demonstrate many different ways of rendering content. The content reuse is a little more challenging.
What I would like to demonstrate is how a single TiddlyWiki can provide a wealth of features and options *on demand* without having to be large. I also hope my solution can maintain its ability to search through all its content. I have begun assimilating the plugins and tiddlers I want to incorporate using Eric's http://www.tiddlytools.com/#LoadTiddlersPlugin to grab them and http://www.tiddlytools.com/#TemporaryTiddlersPlugin to exclude them from being saved in my TiddlyWiki. The repositories of plugins I am referencing include http://www.tiddlywiki.com (for configuration and help content), http://www.tiddlytools.com, http://tiddlywiki.bidix.info/, http://tw.lewcid.org, etc. The idea is to glean the best from these places, always working with the most current version, not duplicating the content by saving it locally, and yet be able to search through it all. Another use case is that I can maintain multiple TiddlyWikis, each dedicated to a particular type of content, yet use this mechanism to keep them synchronized. Content is displayed and searchable but not truly repeated in multiple files. By combining the "temporary" tag with http://mptw.tiddlyspot.com/#HideWhenPlugin I can insure that I don't accidentally edit a "copy" instead of the "original" content. Because I am documenting my process as I go, there is a *lot* of typing involving the use of {{{<<loadTiddlers>>}}} in both an automatic and a manual implementation. For my presentation at school (Mount Royal University) I will have a local copy of all TiddlyWiki repositories (better performance no issues with lack of Internet access) but I would like to be able to "flip a switch" and run the same demonstration loading tiddlers from their true host sites. My real-world version will be based on accessing the remote sites primarily and local copies only if absolutely necessary. What I would like to have is a mechanism (e.g. transclusion, macro, script) that can process a formatted list of Sources (URL or local path to a TiddlyWiki repository) and Tiddler Names: your basic name/ value pair. I prefer the list to be the contents of a single, local tiddler. To address my automatic versus manual design goal, the solution can easily handle choosing between including or excluding the 'label:' parameter. A multi-select listbox would be an excellent UI for the "load some but not all" scenario. Enhancements would include being able to replace the tags of the incoming tiddlers with tags optimized for my TiddlyWiki. This would require the name/value pair paradigm to become something more like a CSV file: column-separated and row-separated. The piece of the puzzle that has me stumped is processing a list of values and pushing them into {{{<<loadTiddlers>>}}}. Tinkering with how {{{<<newTiddler>>}}} handles parameters seemed like it would help but my brain hasn't caught up with my enthusiasm. With the mechanism in place, all I have to do is tweak the list to include or exclude as many or few plugins and tiddlers as I want. If http://www.tiddlytools.com/#ImportTiddlersPlugin had a script UI option that included tag modifications and an 'init' flag, maybe a marriage with http://www.tiddlytools.com/#RunTiddlerPlugin, then I would have a pretty robust solution. Could fET help tie it all together? My questions regarding search capabilities are, "How can I configure my TiddlyWiki to search through the tiddlers of other local TiddlyWikis as well as itself? Whatever has been loaded is searchable but could the remaining external content also be searchable and loadable on demand?" Thank you for any suggestions. Craig -- 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.
