On Saturday, September 26, 2020 at 3:13:59 AM UTC-7, Moe Gibbs wrote: > > I started from scratch and, thus far, and as near as I can tell my > problems resulted from: > > 1. Grammarly. >
There are some browser add-ons that automatically "inject" code into every HTML file you load in the browser. Most of the time, these add-ons do good things, and typically work well with lots of "normal" websites. However... TiddlyWiki is *much* more sophisticated than most websites. It provides a highly-interactive customizable "framework" for doing lots of different kinds of information activities, and is intended to work with a wide variety of systems and browsers... and it does this in a single, self-contained HTML file, without *requiring* installation of any special software on your system (see below, regarding "file savers"). 2. Wonky recommended save methods f/TW site. I'm no coder, but I do know > that software and code goes stale. > There are LOTS of different ways to configure TiddlyWiki to save to your local filesystem. Most of these methods involve installing various "helper" programs that let you work around the rather strict "security" barriers that modern browsers have with regard to accessing your local files and directories. However, there is one method that is *built-in* to the TWCore code, that doesn't require any "helper" programs whatsoever. This method is called the "default download saver", and uses your browser's standard "download a file" interface to save changes to your TiddlyWiki files. In effect, each time you "save" the file, it is really doing a "download"... even when the file was loaded from your local filesystem. Most browsers have settings you can configure to tell it how to handle downloads. In particular, you can tell your browser to "always ask where to save the downloaded file", rather than having it use a fixed location (e.g., the standard "Downloads" folder). After setting the "always ask" option, each time you "save" your TiddlyWiki, you will be prompted by the browser to select a folder and enter or select a filename. If you choose an existing filename, you are asked to confirm overwriting that file. Some browsers will automatically suggest a number that is added to the filename (e.g., "(1)", "(2)", etc.) to avoid accidentally overwriting a file. I will often use the automatic file numbering feature to save "checkpoints" as I work, so that if I break something, I can just reload the previously saved version. Once I am confident that I've got things working the way I want, I can then use the "download saver" to select the original filename and overwrite it. Then, I can use my system to select all the "checkpoint" files and delete them, leaving just the one file remaining. All of the above is accomplished without using any "wonky" file saving methods, and will *never* "go stale" because it uses your browser's code to do the work. As long as you keep your browser up-to-date, the "download saver" will *always* work. Advise some kind of quality control/currency checker for official plugins, > themes, and save methods. > Do keep in mind that TiddlyWiki is an all-volunteer "labor of love". There is no funded organization to pay for someone to perform full-time "quality control" checks. Even so, we try our best to keep things working properly... but to do this, we must rely upon the help and cooperation of the general TiddlyWiki user base to report problems and then work with us to solve them. -e -- 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/575150d2-d1c1-42a5-a659-2af06a044e3fo%40googlegroups.com.
