The include plugin: http://tiddlywiki.abego-software.de/#IncludePlugin
lets you selectively bring in sets of tiddlers. You have to edit these tiddlers in their source document, which is usually OK for archived material. Eric Shulman's ExternalTiddlersPlugin will bring in one tiddler at a time via a macro. It will create a tiddler for you on the fly, if that's what you want, so that you can then proceed to edit the resulting tiddler. A real database would be a drag on portability. You can spend all day tweaking something like MySql, worrying about permissions, users, access levels, etc. But if you can interface with Java or Python, I believe there are sql-style programs out there (Gadfly? On python) that would be somewhat less unwieldy. If there is a way to connect to "C" programs, then I'm sure there must be ancient code for x-base file retrieval programs, which, though now deprecated, would be faster than the javascript engine and (probably) allow larger databases. -- Mark On Aug 19, 5:52 am, Tobias <[email protected]> wrote: > Some random thoughts > > As for (pseudo) databases... would a json interface be a good apporach > to externalize content? > > Or, how about pulling collections of tiddlers individually, such that > you'd have a basic tw setup (separate core, plugins, themes) and load > content tiddlers from such external "bags" (where'd I get that term > from? ;o), chosen via a simple dropdown. > > Why? For one, you wouldn't have megabytes of content in one html file > and could split up your content into meaningful categories (each one > represented by a different file ...json or simply html "snippets"). > > This could be managed by a general routine, whereas you would simply > flag any external file with some sort of "always load" flag (or simply > put it into preMarkupHead?), indicating that you want to include that > content on startup rather than switch to that category at > runtime ...like help, info, dictionary or todo tiddlers that you'd > personally want always available, but not intermingled with your setup > (core, plugins & themes). > > In other words... if anyone has a quick tutorial or routine on how to > externalize certain tw elements into different files, withouth the > need of tiddlyweb or such, please share... though I guess that would > require some adaptations as to loading and saving routines, some sort > of "externalizePlugin". > > Tobias. > > On Aug 19, 12:46 pm, AlanBCohen <[email protected]> wrote: > > > Just a side comment after looking at > > thehttp://jackparke.googlepages.com/jtw.html#SQLQueryPlugin > > mentioned by Wolfgang. It appears to be able to issue queries to an > > existing database (of various kinds), but I would suspect that the > > databases are unlikely to be portable in the same way as the wiki > > itself. This would be fine for a wiki located in a stationary > > directory on a known network, but doesn't currently meet my needs for > > portability across OS's. I was looking to jquery for this. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
