Hi dam > > Well, I've just seen that accessing the original shadows is possible using > the subtiddler attribute of the set widget. If there are also other ways, > please let me know. Automatizing the alert and diff log could be an idea for > a plugin, if there are none already doing the same thing.
You can also access subtiddlers directly with the view and transclude widgets. There's also a "subtiddlerfields" filter operator for reading the names of fields within a subtiddler. Best wishes Jeremy > Thank you, > dam > >> On Sunday, March 6, 2022 at 4:21:52 PM UTC+1 damscal wrote: >> Thank you very much Mario and Jeremy. I have proposed the additional cascade >> on github, hopefully it can be implemented in one of the future upgrades. >> >> Coming back to the main topic, is there a standard way to >> reference/transclude a shadow tiddler that was replaced by a standard >> tiddler? >> This would make possible overwriting a shadow tiddler with a standard >> tiddler that is dynamically derived from the shadow itself, even after a >> plugin upgrade. >> >> Example: >> user overwrites the shadow $:/plugin/some-tiddler with a standard tiddler of >> the same title >> the original shadow tiddler can be accessed/referenced with the title >> $:/plugin/some-tiddler/overwritten (or an equivalent way) >> the user can write wikitext inside $:/plugin/some-tiddler which references >> $:/plugin/some-tiddler/overwritten , e.g. through something like {{{ >> [{$:/plugin/some-tiddler/overwritten}search-replace["text to >> replace"],["replace with this"]] }}} >> when there is a plugin upgrade, $:/plugin/some-tiddler/overwritten gets >> automatically updated. If the new version is different, a log reminds the >> user to review the diff to check that things aren't broken. >> if the plugin upgrade makes the customisation obsolete, the user can simply >> delete $:/plugin/some-tiddler >> Thank you all, >> Dam >> >>> On Sunday, February 27, 2022 at 4:49:45 PM UTC+1 jeremy...@gmail.com wrote: >>> Hi damscal >>> >>> It's a good idea. The best way forward might be to propose a core change to >>> introduce an additional cascade for the template used to display the >>> content of a tag pill, so that users can have tags with custom appearances. >>> >>> But to answer your question directly, there is no standardised way to >>> modify core templates without breaking subsequent upgrades. We try to >>> introduce mechanisms for common use cases to avoid modifying templates >>> directly, but it's still the last resort for people wanting to do >>> particularly intricate customisations. >>> >>> Best wishes >>> >>> Jeremy >>> >>>> On Sunday, February 27, 2022 at 3:33:26 PM UTC PMario wrote: >>>> Hi, >>>> If you would be a bit more specific, what you want to do exactly, it may >>>> be possible to provide some pointers. ... May be your ideas are also >>>> suitable to improve the core UI in a generic way. .. If so .. It may be >>>> possible to implement some new stuff directly into the core. . >>>> -mario > > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/c9a24c52-f8f5-4626-bada-b7909fa0c8a4n%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/DD66DA67-E1DD-4AE1-AB1D-8147C50D9793%40gmail.com.