Mass update of plugins in multiple TiddlyWikis

[Mrown]

Hi,
I currently have dozens (if not more) of TiddlyWikis, each covering
a topic of interest. I use a template with the plugins that I
currently find useful to create any new TiddlyWikis. However, if a
plugin is updated and I want to update the corresponding plugin across
all the TiddlyWikis, how would I go about doing so? Also, if
TiddlyWiki itself is updated and I want all the old TiddlyWikis to
update to it, how could I go about doing so? Thanks for your help.

[Dave Parker]

I've started using IncludeTiddlersPlugin to make changes to one TW's
main menu (using <<tiddler TemplateMainMenu>> referring to an
alternate menu). Any time I make a change in the one its reflected in
the others. I don't know for sure if this would work for plugins
(ie, just include the file that has the plugins you want), but its
probably worth looking into.

hth
DP

[Eric Shulman]

> a topic of interest. I use a template with the plugins that I
> currently find useful to create any new TiddlyWikis. However, if a
> plugin is updated and I want to update the corresponding plugin across
> all the TiddlyWikis, how would I go about doing so? Also, if

http://www.TiddlyTools.com/#LoadTiddlersPlugin

provides automatic one-click import of remote tiddlers with filtering
based on "new", "changes", "updates", etc. When tiddlers are imported
using <<loadTiddlers>>, they are copied into the current document as
"real" tiddlers and can then be edited and will be saved with the file
(unless you also use
http://www.TiddlyTools.com/#TemporaryTiddlersPlugin
to tag the imported tiddlers as "temporary"). Note: when plugins are
imported, you will need to save-and-reload the document for those
updates to take effect.

HTH,
-e
Eric Shulman
TiddlyTools / ELS Design Studios

[wolfgang]

Hi Mrown and Dave,

Plugin Tiddlers of included TiddlyWiki files will show up in the
plugin manager of the back stage - with the log message: This plugin
has not been executed because it was added since startup. But since it
only will by added at startup again - once you do a save and reload -
it will never go beyond being added at startup. :-(

However, there are ways to not only to load - put also have them as
functioning plugins - by placing them separately in a folder on a
drive as .js files. Where you only would have to update the particular
plugins .js in that folder - and all TiddlyWiki who load their plugins
from this folder automatically would be up to date.

One way to do this are Bookmarklets in the way of
http://xdexavier.googlepages.com/yoursearch.html, pointing to the .js
to include.

An other is LoadExtPlugin of BramChen (http://ptw.sourceforge.net/
ptwe.html#LoadExtPlugin).

A third prerelease - but nevertheless working possibility is what I
talk about in the thread: "ExternalTiddlersPlugin (or
LocalAdaptorPlugin) request" by using loadExternalv2.js (http://
groups.google.com/group/TiddlyWikiDev/attach/24b01004700c20a6/
ExternalTiddlers.zip?part=4) with the added amazing ability to load
virtually any file type as a tiddler.

Fourth, LocalAdaptorPlugin might (or might) not by able to be used for
this, once it will be released.

Fifth, by placing the path of a plugin .js into the MarkupPostBody
shadowed tiddler - that plugin would also be included as a functioning
plugin.

Regards,

W.

[wolfgang]

> ... Also, if

> TiddlyWiki itself is updated and I want all the old TiddlyWikis to
> update to it, how could I go about doing so? Thanks for your help.

For sure take a look at BramChen's PrintceTiddlyWiki (http://
ptw.sourceforge.net/ptwe.html#LoadExtPlugin) - because it does not
only load the plugins from external .js - but also the TiddlyWiki
core. Here you would have just have to exchange the twcore.js with the
latest release - and all your TWs are up to date.

W.

[wolfgang]

> > a topic of interest. I use a template with the plugins that I
> > currently find useful to create any new TiddlyWikis. However, if a
> > plugin is updated and I want to update the corresponding plugin across
> > all the TiddlyWikis, how would I go about doing so? Also, if
>
> http://www.TiddlyTools.com/#LoadTiddlersPlugin
>
> provides automatic one-click import of remote tiddlers with filtering
> based on "new", "changes", "updates", etc. When tiddlers are imported
> using <<loadTiddlers>>, they are copied into the current document as
> "real" tiddlers and can then be edited and will be saved with the file
> (unless you also use

Of course, for a TiddlyWiki beginner, this is a much less complicated
and easy - though manual - way to update all TW to the latest change.
Additionally, it also remains truthful with the one file philosophy.

Where with my above mentioned methods you would have to remain to a
certain extent with the indicated folders.

Regards,

W.

[FND]

> I want to update the corresponding plugin across
> all the TiddlyWikis, how would I go about doing so?

If you knew a little bit of Ruby, you could use r4tw:
http://randomibis.com/r4tw/

-- F.

[wolfgang]

Hi F.,

What would one have to learn, to know a little bit of Ruby? - Anything
recommended?

Regards,

W.

[FND]

> What would one have to learn, to know a little bit of Ruby? - Anything
> recommended?

I hardly have any experience with Ruby myself, but Daniel had suggested
this tutorial to me a while ago:
http://tryruby.hobix.com

That of course doesn't introduce you to the functionality provided by
r4tw - but the examples on the r4tw site should be easy to understand.

-- F.

[wolfgang]

Thanks for passing the recommendation of Daniel on.

> That of course doesn't introduce you to the functionality provided by
> r4tw - but the examples on the r4tw site should be easy to understand.

looked at the r4tw site and was at a loss understanding anything.
So hopefully http://tryruby.hobix.com/ will indeed make understand the
context of it.

Regards,

W.

[Eric Shulman]

> >http://www.TiddlyTools.com/#LoadTiddlersPlugin
> > provides automatic one-click import of remote tiddlers with filtering

> Of course, for a TiddlyWiki beginner, this is a much less complicated
> and easy - though manual - way to update all TW to the latest change.

If you omit the label="..." parameter from <<loadTiddlers>>, it will
be invoked as soon as it is rendered, rather than waiting for a click
on a command link. Then, if you place the <<loadTiddlers>> macro into
your MainMenu, and it will be invoked *automatically* each time you
load the document.

Note: instead of putting <<loadTiddlers>> or similar "startup macro"
into the MainMenu, you could put the macro into a separate tiddler
(e.g., [[SiteStartup]]), and then invoke *that* tiddler directly from
a hidden span in the PageTemplate, like this:

<span macro="tiddler SiteStartup" style="display:none"></span>

Then, whenever you want to add/change the startup macro definitions,
you can just edit [[SiteStartup]], instead of putting non-menu content
into [[MainMenu]] (which always seemed a bit counter-intuitive to me,
anyway)

[Daniel Baird]

Even if you get what you need from the r4tw examples, I still
recommend learning Ruby. Writing code in ruby aligns all the chakras
that Java / C++ / Perl / PHP put out of place :)

Cheers
;Daniel

--
Daniel Baird
NERD JOKE: 2x12=24. 1x12=12. 0x12=18.

[wolfgang]

> Even if you get what you need from the r4tw examples, I still
> recommend learning Ruby. Writing code in ruby aligns all the chakras
> that Java / C++ / Perl / PHP put out of place :)
>
> Cheers
> ;Daniel

Hi Daniel,

I seem to have a good intuitive immune system - what other reason for
refusing to learn these scripts - than for not falling completely out
of balance. ;-

So when I heard Fred talk about only having to learn "a little bit" -
that sounded interesting indeed.

But seriously, how did you mean that with aligning? - In which way the
other scripts are putting off?

However, since you voiced that there is "no little bit" - please also
tell me out of hand experience about the addictive propensities of
Ruby first.

Because in this respect these different scripts now seem just alike?

Regards,

W-