# Another approach Every wiki would have tiddlers.json. This JSON could be any of (I think we need to support all 4 methods): - a file served by regular web server (github.io or apache or caddy or whatever you want) - served by bob - served by nodejs tw web server - regular tiddler
The file would be in the same format as expected by lazy loading mechanism present in TW5. IRC the JSON structure is a list where every item of the list is a map which includes all the fields of the tiddler except text. I.e. it would have tags, fields, title, caption and so on. I think the main wiki could have links to all locations where subject wiki are located. Here is how it might work from user perspective. 1. We can have special tag to mark dependent wiki sources. Something like $:/plugins/multiwiki/Source 2. We tag new tiddler (let's call this kind of tiddler SourceWiki) with tag $:/plugins/multiwiki/Source. This tiddler would have _canonical_uri which points to tiddlers.json 3. We would have a filter which finds all tiddlers with that tag. 4. I could extend split-web plugin to support - multiple tiddlers.json sources - use SourceWiki tiddler name as a namespace. I.e. as prefix for each imported tiddler. 5. In this case all external tiddlers would appear to be local. We would need to modify view template to: - provide visual indication that it is external read only tiddler - add visual element to open external tiddler in new browser window or tab (in the context of subject wiki) The reason I think this approach is viable is because it uses existent TW5 lazy loading mechanism. It also makes external tiddlers first class citizens (the only difference is they are read only). Best regards, ILYA >> >> - Tiddlywiki is great at small to moderate number of tiddlers >> - It is easier to keep few subjects in a Tiddlywiki, for example a >> student can have one wiki per course >> - I see Tiddlywiki like a MsWord file but with tons of features >and >> suprior flexibility >> - I see Tiddlywiki as a webpage, but simple to create, >customize >> and use >> - I see Tiddlywiki as a database >> - RESULT >> - People using Tiddlywiki have several separate Tiddlywiki >> - ISSUE >> - Searching and finding something gets difficult and makes >headache >> >> >> One solution >> >> - create a master Tiddywiki or a main wiki >> - use a dataTiddler per wiki to index few fields per tiddler like >> tiddler titles, caption and keywords field >> - put all these indexes in the master Tiddlywiki >> - Use the standard or advanced search to look in these indexes and > >> return a link to the correct wiki >> >> Howto >> >> - a simple script to create or update the index in the wiki >> - export the updated index to master wiki >> >> I know about Twedration, but this is a simple solution for whom use >single >> html Tiddlywiki. >> >> >> 1. What do you think? >> 2. Have you seen such solution before? >> 3. Can you share any tools, idea? >> >> --Mohammad >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/579F518B-26DB-41F4-8B34-8F721A3DA4A5%40gmail.com.
