Dear TiddlyTweeter,
You are correct and JSON bundle could be a practical way to solve the issue
once or few times.
Actually I have many wikis where I need to load the same customization.
Therefore I need to maintain it in a single place and share with many
wikis. I found two ways to achieve
Isn't the issue here overwrite priority?
I found that PMario's Bundler plugin good for that since it can force
overwrite. Of course you need do it in the correct order. Which is what, in
a way, you are saying.
My point is do you need bother with a new plugin at all when JSON import
can
Last minute thought.
Why not to invert the logic in the core (two lines in the code of boot.js):
1. core
2. plugins with no priority defined in alphabetical order
3. plugins with priority defined ordered ascending by priority
This way one would have the chance to force plugin
Hi Tony,
*Examine the changes both plugins make to the shadow tiddler and construct
> a third that incorporates both changes and add it to your package so it is
> applied last. This condition is only true when you use your package so it
> makes sense.*
>
Your suggestion is good, but not very
Looks like this issue may be reduced in future
https://groups.google.com/forum/?hl=en#!topic/tiddlywiki/zpzMoGUGM0g
If the difference is about widget changes.
Regards
Tony
On Sunday, March 17, 2019 at 4:09:25 AM UTC+11, mauloop wrote:
>
> I have a bunch of tiddlers that I use to import in every
Thanks, Matt and Jed. You've been very kind and exhaustive.
Now it's clear to me what happened and why I had to force priority for certain
tiddlers and not for others.
Regards, )+(
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To
A suggestion,
Examine the changes both plugins make to the shadow tiddler and construct a
third that incorporates both changes and add it to your package so it is
applied last. This condition is only true when you use your package so it
makes sense.
To do this take a vanila wiki, an use a
I Matt is correct. In the code correctly the core is added first then the
other plugins are sorted by name and added in order from a to z then any
plugins with a priority field with later tiddlers taking precedence over
earlier ones.
A more detailed description of the sorting:
Plugins with a
My experience has been that the winning tiddler is based on alphabetical
order, last plugin wins. So $:/plugins/mmm would be overwritten by
$:/plugins/zzz but not $:/plugins/aaa. But I would be careful of expecting
any hard and fast rules here, as I don't think the behavior is explicitly
9 matches
Mail list logo
