Instead of admiring Jed's work from afar, I'm finally joining the cool kids in wading into his TW5 BobEXE edition (implementation?).
Having never used TW5 on Node.js beyond the initial setup, I'm having to grapple with the concepts of a server-based TW again and get used to some of the differences. So I thought I'd create a thread here for my newbie questions and discussion. It may end up a junk drawer of conversation, but hopefully it will record some of my confusion and point others who come after me in the right direction. 1. Is there a good general reference/tutorial for getting started with Bob? The best I've found has been Jed's gentle, step-by-step prodding through the tiddlers in his edition But I had to decide I wanted to try the BobEXE version, find it, and run the executable before I got into those. (Fellow noobs, if you don't have the .exe file yet, start with the ReadMe here: https://github.com/OokTech/TW5-Bob ) 2. Is there a configuration option to disable the launching of the default Ooktech/Bob TiddlyWik when the *bob.exe* starts up? I find I'm crashing the server a lot during my initial setup, exploration, and import of tiddlers. It would be nice not to have to close additional instances of the "BobHub" page every time I restart the *.exe*. 3. Is there a configuration option (or hack, even?) to point the *.exe* to a different path? (E.g,, could I keep the *.exe* in */ProgramFiles* on my *C:\* drive and my related folders in */TiddlyWikis* on my *D:\* drive?) 3a. One reason I ask about this is I like keeping TWs in a folder that syncs to my cloud storage account, but that storage service doesn't like having *.exe*s running in a location it's trying to sync. Any insights on this from any Bob users. (This leads directly to my next question.) 4. What's the best strategy for backing up Bob-based wikis? Just synchronizing your */Wikis* folder to another location? 5. What's up with those *.meta* tiddlers Bob sometimes creates? At first, I thought that's how it was keeping track of as-yet-unsaved changes to tiddlers, but that doesn't seem to be the case. 6. A higher-level (and hopefully simpler) question: What are the advantages of using a Bob-powered wiki over the single HTML file? Related to that last question: I have some old TiddlyWiki Classics where I dumped the contents of reference articles to make them easily sortable and cross-linkable, but once that hit a certain size, I started breaking the articles out into related TWs because the load and save times got ridiculous. Nowadays I'm starting to keep detailed "how to" TWs to remind me of procedures and settings, but they too can get large. Am I right to hope Bob, by virtue of not having to parse *all* the HTML of every tiddler every time it loads or saves, might make TWs with lots of large tiddlers more feasible to work with? *That's — a lot for one post, isn't it? I'm hoping some of these have a complete answers elsewhere in the group or around the Web and some kind soul will post links to existing discussions or documentation.* -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7dd25fbd-a38c-4f97-a682-0eccba40e04c%40googlegroups.com.
