Hi David I wasn't suggesting that git was a universal solution, more that it's one of many techniques that users with different prior experience can use to manage multiple revisions of their files. Dropbox doesn't require any prior technical experience.
TiddlyWiki's single file format means that anybody who understands how files work can easily make a backup just by copying their files to a safe location. As to the plugin clash you refer to, it's relevant that Tobias's plugin makes use of an incredibly dangerous technique that we have long implored people to avoid: the plugin overwrites one of the core JavaScript modules. I appreciate that there is no way of knowing that if you encounter the plugin today, but there it has a somewhat controversial history. When the project started the idea was that community plugins would be encouraged to migrate to the official plugin library. As it's turned out, that's quite a lot of hassle for developers and so instead we have the current situation where plugins are dispersed and there's no easy way to find out their provenance. (Thinking about it now, we could indeed add a big red banner that appears whenever a core JS module is overwritten... Harder to extend that to non-JS tiddlers since quite a few of them are designed to be overwritten if required). Best wishes Jeremy. -- Jeremy Ruston [email protected] https://jermolene.com > On 3 Mar 2019, at 00:59, David Nebauer <[email protected]> wrote: > > What you say is correct, Jeremy, and I'm already version controlling my wiki > and keeping my personal customisations in plugins, and yet... your comments > trigger a couple of thoughts. > > The first is that TW is "marketed" as a personal notebook as much as a > personal wiki. The second sentence at tiddlywiki.com is "Welcome to > TiddlyWiki, a unique non-linear notebook for capturing, organising and > sharing complex information." If TW is intended for use by ordinary computer > users, as opposed to software experts or power users, it may not be > reasonable to expect them to be git wizards able to use git bisect and others > techniques to track down a breakage. > > The other thought is that I've seen several suggestions in this group that TW > is in the first stages of an explosion of > creativity/development/customisation now that it has reached a sufficient > degree of maturity. If true, this is going to expose a great deal more of the > brittleness you refer to as multiple plugins and components interact with > each other. For example, a recent topic reported that two plugins both > replaced the same core tiddler, breaking one (or was it both?) of them. As > another example, AFAIK TW won't warn a user if they create or import a > tiddler, or install or upgrade a plugin, that overwrites a variable, macro or > filter defined in an existing tiddler/plugin; nor is there a canonical list > available anywhere that lists variables, macros and filters provided by > custom plugins, so developers of new plugins (or just personal > customisations) can avoid name collisions. (This risk can obviously be > minimised by plugin- or user-specific prefixes.) > > These comments are made as a recent convert to, and huge fan of, TW(5). > > Regards, > David. > >> On Sat, 2 Mar 2019 at 23:42, Jeremy Ruston <[email protected]> wrote: >> I think the problem you’re describing is the possibility that ones delicate >> arrangements of customisations might break, perhaps through an upgrade or >> human error. That’s certainly something I can relate to, and I’m interested >> in how we can address the brittleness of complex wikis. >> >> The primary defence is to keep continuous backups. >> >> Further defences include making your customisations into a plugin. > > -- > 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 https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/CAFWVPz_P8ZR92Y8hqrdXsyjoYGiCPAVAOFNtqT09%3DxJNckrDug%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7EB35719-FB26-49D7-8FDE-C347FD35E13D%40gmail.com. For more options, visit https://groups.google.com/d/optout.
