Ignoring the unhelpful first reply post, Taspie, the main problem with your idea is not about processing the content into a TiddlyWiki. The main problem you will face *after* successfully creating a TiddlyWiki holding the entire contents of the Bible, Koran, or any similarly large body of work is performance. In my experience (and YMMV), once a TiddlyWiki holds more than a few hundred tiddlers, approximately 2 MB or so, it begins to perform sluggishly: * load time will be loooooooong * the size of the HTML file and the availability of sufficient memory might make searching and rendering slow * some browsers just don't handle large files well
Possibly the most efficient TiddlyWiki-based solution would involve a marriage of an index of tiddlers (reasonable in quantity and size) pointing to numerous external files (tiddlers), loaded on demand, containing the bulk of the content. There are still ways to search this multi-file TiddlyWiki. But the most obvious downside to this approach is that *all* the files must be kept together. Now your TiddlyWiki solution won't be a single-file solution. Not meaning to rain on your parade, Craig -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev?hl=en.
