Hi Stephan
- I understand that the tiddlers inside a plugin are considered shadow
tiddlers regardless of the name but I don't understand the why. Is it
simply the fact they are in a plugin that makes them shadow tiddlers?
It is to keep all tiddlers of a plugin bundled so when
Shadow tiddlers are special system tiddlers. They are there, that users can
change the default behaviour. ... But if something goes wrong, the user can
just delete the modified tiddler and the system tiddler will take over
again.
TiddlyWiki always used this behaviour as a backup feature. ..
Tiddlywiki automatically prefixes the plugin tiddlers with the plugin
prefix so this can't happen.
Eventually, there will only be one GettingStarted that wins.
So, I believe Stephen's question is: Which and why?
Best wishes, Tobias.
--
You received this message because you are subscribed
Hi Stephen,
I understand that the tiddlers inside a plugin are considered shadow
tiddlers regardless of the name but I don't understand the why. Is it
simply the fact they are in a plugin that makes them shadow tiddlers?
http://tiddlywiki.com/#ShadowTiddlers — if you feel like something
Which and why?
I think it's entirely down to the order in which the tiddlers get loaded
into the wiki. A later tiddler of the same title will override an earlier
one.
The order may differ between Node.js and the browser.
See *$tw.loadTiddlersBrowser()* and *$tw.loadTiddlersNode()* in
The order may differ between Node.js and the browser.
See *$tw.loadTiddlersBrowser()* and *$tw.loadTiddlersNode()* in
*$:/boot/boot.js*.
I get the feeling that it's not the best idea to overwrite a core component
using a plugin.
After all, two plugins may want to do the same and then
Hi Stephen
I understand that the tiddlers inside a plugin are considered shadow
tiddlers regardless of the name but I don't understand the why. Is it
simply the fact they are in a plugin that makes them shadow tiddlers?
Yes, although the logic makes more sense the other way around: shadow
