Hi again, Stefan, > Thank you for the quick answer. So if I want to work with TW I should use > the node version or *multiple small TW5 wikis and index and search their > content with Windows Explorer*. > The benefit of using node would be to have neatly chunked tid files, rather than wikis to search. What is missing as of yet is a parser / indexer that semantically searches tid files, e.g. certain fields, like tags or title or text, or date fields, etc.. A CLI (and possibly a ui on top) would surely majorly enhance the node experience.
Node is not so user friendly and I would need a manual to use TW in command > line under Node. I certainly see how using a CLI comes with a barrier and requires a greater willingness to learn and remember and perhaps a need to often use certain commands, to not having to constantly look up the right one and its spec. (also it stores all embed media files in a single folder which could lead > with a huge mess). There may be a default storage location for embedded content. However, you are not bound to use that, you are quite free to organize both tiddlers and external files in any way you find suitable to your project(s). In fact, your folder structure and the eventual titles / addresses of those tiddler sin your wiki are entirely independent. Does TW5 on node.js can face the same problem with huge amount of text and > image tiddlers? I think on node it is much easier to manage tiddlers in whichever wiki / folder structure you want and to cross include different components into whichever build / bundle / aggregated wiki you want to eventually create, Best wishes, — tb -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/75dfb004-fbc1-435f-be14-8bc854310a07%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
