On Monday, March 13, 2017 at 9:08:25 PM UTC-7, tejjyid wrote: > > I develop my TW code inline; currently from a file, as there's a lot to do > handling the upgrade to TW5, but hopefully, in the future, from the browser > again. I would routinely save & reload a TW tens, and possibly hundreds of > times in a coding session. This is going to be an much more unpleasant > experience if I have to go back to the filesystem to open a new file after > every save, as well as delete the large number of old and dysfunctional > copies of the file which might be dangerous to leave around. >
Your workflow always overwrites the index.html "tens, and possibly hundreds" of times in a coding session. If that's how you prefer to work, that's fine by me. However, it's a bit like walking the high-wire without a net: if something you just wrote causes a fatal error at load time (the dreaded RSOD), correcting those changes could be very problematic, since you aren't keeping backups along the way. Depending upon how much is changed with each save, it might be a real headache to isolate the source of the fatal error without having a nice "diff" of those changes to compare. However... even with my suggested "download saver" workflow, you can achieve the exact same "high-wire" results simply by always selecting the base index.html to overwrite each time rather than creating additional numbered 'checkpoint' saves. Of course, this *does* add two actions to your existing workflow: a double-click to select the "index.html" filename in the list and a single-click to confirm the "are you sure?" popup, but I feel that this adds a very minor inconvenience at worst, and provides a valuable 'sanity check' before actually committing to a non-recoverable overwrite of the primary work file. In addition, after you have allowed the overwrite to proceed, the rest of your existing workflow (i.e., reloading the saved file to test and continue working) remains exactly the same: you reload the current document simply by pressing the browser's reload command (ctrl-R or alt-f5 in Chrome). There is absolutely no need to "go back to the filesystem" after ever save and, since you aren't actually creating 'checkpoint' saves, there are also no "old and dysfunctional" copies to clean up afterward. Also note that if you DO choose to create 'checkpoint' saves along the way, you still usually don't have to go back to the filesystem to open them, since many browsers provide some kind "download status bar" output that includes a button to quickly open the newly saved file with just one click. Sure, you have to remember to clean out the left-over checkpoint files at the end of your work session, but it is typically a very easy operation to select the unwanted files (i.e., using shift-click to select the whole set at once) and then pressing 'delete' (or dragging to the trash)... and if you're using a command line environment (i.e., a Linux shell), then it's even easier to clear out the files with just a single "rm index*(*).html" command enjoy, -e Eric Shulman TiddlyTools: "Small Tools for Big Ideas" (tm) InsideTiddlyWiki: The Missing Manuals -- 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 post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2534c4ea-97b3-44f0-8b33-7738d5616335%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
