Hi David 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. Given that TiddlyWiki is reasonably small by the standards of modern digital photos, and disk space/cloud storage is fairly cheap, it’s reasonable to keep a backup of every change we make to our wikis. I use git for some wikis, and for some personal stuff in standalone HTML files I rely on a Dropbox Pro feature whereby every previous version of a file is backed up and available for restore. With continuous backups one can rewind time to find and fix problems made in the past. Further defences include making your customisations into a plugin. That makes it easier to move the customisations between wikis, but it also lets you keep track of any modifications to them. Best wishes Jeremy. > On 2 Mar 2019, at 08:50, David Nebauer <[email protected]> wrote: > > S. S., no problem. I touched on it in a post earlier in the topic. My use > case is that I've been using TW for a couple of months now and am starting to > include some macros in my tiddlers that are either defined in standalone > macro tiddlers or in non-core plugins. One example is Mohammad's <<dbadge>> > <https://kookma.github.io/status-badge/> macro which I rolled into a > home-made plugin. When I realised that a call to a missing macro does not > result in any error display in the tiddler, it occurred to me that there > would be no warning if a macro tiddler was deleted or, if it is defined in a > plugin, disappeared or was renamed in a plugin upgrade. That got me to > wondering if I could include a tiddlyscript snippet at the top of any > tiddlers which rely on non-core macros to check for the existence of said > macros and display a warning if the macro is not defined. > > I realise this is worrying about a very unlikely scenario but, if I'm going > to be using TW as a personal notebook for years, and likely across multiple > computers in that time, I tend to be paranoid about "future-proofing" and > chains of dependency. > > There may be better ways to approach this issue; if so, I'd love to hear > about them. > > Regards, > David. > > On Friday, 1 March 2019 13:16:51 UTC+9:30, S. S. wrote: > David, it was an interesting question. Could you share what happened for you > to want that feature, and how you are using it? > > On a similar track - the code in the <<dumpvariables>> macro can show the > values of all variables and macros that exist at that position in the widget > tree. I wonder if it would it be useful for developers (or even users who > type macros) to be able to have a way to check against that list to see if > ANY variable that is in the widget tree is undefined, and that could be used > to trigger a warning on any refresh and display the undefined > macros/variables? > > Regards > > -- > 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] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywiki > <https://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/0b2f7c7d-8513-4bb9-92d6-d21cd69dbb57%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/0b2f7c7d-8513-4bb9-92d6-d21cd69dbb57%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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/00B96DDD-7492-4A0E-92BA-1714B6BBD2DD%40gmail.com. For more options, visit https://groups.google.com/d/optout.
