On Jun 19, 10:53 pm, wolfgang <[email protected]> wrote: > But to keep many plugins as separate .js files up to date takes much > more time, than to use one MasterTW with all plugins updated through > the backstage sync utility. With MasterIncludesPlugin in the slave > TW's installed, it then load a bunch of individual plugins marked with > a distinct tag automatically at startup. >
Thanks for the idea. I've been unable to find anything about the MasterIncludesPlugin, so I'm not sure how it worked. Udo Borkowski's IncludePlugin (at http://tiddlywiki.abego-software.de/#IncludePlugin and documented at http://tiddlywiki.abego-software.de/#[[IncludePlugin%20Documentation]] ) seems to do much of the same thing. The documentation is a bit unclear about how well it handles included plugins. It says, "the includes listed in the "IncludeList" are processed at TiddlyWiki startup," so hopefully this will have the same effect as tagging a plugin with systemConfig. I'll have to try it. If it works, you're right. Keeping a master TW with plugins is better in most instances than keeping a separate library of *.js files. If this doesn't work, I'm back to square one, although maybe there's some way to hack the plugin and get it to work. This, however, still leaves two unresolved issues. First, rather than manually type complex paths for each included plugin, I'd rather be able to set symbolic path variables, as is typically done in shell scripts. This has the advantages of (1) making changes to a file's location easy to implement, (2) having multiple master include libraries for different purposes easy to see with descriptive variable names, and (3) saves typing. The question is how to implement such variables so they're always available before the plugins load. I suppose one could write a plugin to do this and included it first in the IncludeList. I'll have to experiment. The second problem is more serious. Davide Cervone developed jsMath as an entirely separate package for typesetting mathematics within web pages (see http://www.math.union.edu/~dpvc/jsMath/). The jsMath plugin simply initializes jsMath within TiddlyWiki, and its latest version uses Ajax to load the full jsMath.js script from a separate file. I have been unable to get it to load the script unless the latter resides in a subdirectory of the directory where the TiddlyWiki page resides. This is a common namespace problem with Ajax, and thus far I've been unable to overcome it either by working with Ajax calls (this is my first exposure to Ajax) or jQuery's getScript. (I'm using TW 2.5, which is supposed to include jQuery.) Moving the jsMath directory out of the path containing the TW file is important. Not only is the jsMath large, it also over 25,000 files (mostly images for font substitution). I work out of three different offices and use Windows Live Sync to keep my computers up to date. WLS works fine, but it has a limit of 20,000 files for any one sync. Hence, I can't synchronize my TiddlyWikis if jsMath has to be in a child subdirectory. Also, since jsMath is not a TW plugin, I can't use backstage to maintain it. It would be much easier to have only one copy of jsMath and update it as necessary. What's interesting about all these issues is that they would seem universal. Maintaining a library of plugins rather than including separate copies of plugins in every copy of a TW makes obvious sense. So does the ability to access and include javascript packages outside the path of the individual TW. So does the use of symbolic variables for things like paths. How do the rest of you deal with these issues? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
