Scott - thanks for the great description, and also for your "how I use STP" example! -- David
On Sun, Aug 25, 2013 at 6:11 PM, Scott Simmons <[email protected]> wrote: > Hi, David — > > As a fan of SharedTiddlersPlugin, here's what I've observed: > > INCLUDE on its own makes specified tiddlers from a target TiddlyWiki > available in the current TW -- but it doesn't copy anything into the > current file. Plugins included this way can be viewed, but they won't be > activated for use during the TW session. (e.g. <<include > "file:///path/to/myOtherTiddlyWiki.html" filters:"[[MyPlugin]]">>) > > INCLUDE ... EVAL does mostly the same, but it allows you to activate (run) > *most* plugins without having them in your local TiddlyWiki. (e.g. <<include > "file:///path/to/myOtherTiddlyWiki.html" filters:"[[MyPlugin]]" eval>>) > As a general rule, this works great with plugins that define macros that > do something when you call on them, but not so great on plugins that affect > your TiddlyWiki from startup. > > INCLUDE ... IMPORT:N actually copies tiddlers from the target TiddlyWiki > into your current TW. Once you "Save Changes," the imported tiddler will > remain in that TiddlyWiki, even if you disable and uninstall > SharedTiddlersPlugin. (e.g. <<include > "file:///path/to/myOtherTiddlyWiki.html" filters:"[[MyPlugin]]" import:4>> > ) > > I don't see much need to use both EVAL and IMPORT:N parameters in an > include macro. If you're importing a plugin, running it as an evaluated > include will be redundant. The only advantage I see if you wouldn't have > to reload your TW after executing the <<include>> macro to make the > imported plugin available -- but that would only be true ONCE. The next > time you load the TW, the plugin is already present natively. > > *IMPORTANT NOTE:* > * > * > At present, you *CANNOT* import from remote TiddlyWikis (on a different > domain name or a different computer on your local network). That means you > can't do things like: > > <<include "http://www.tiddlytools.com/"; filters:"[[EditTiddlersPlugin]] > [[ForEachTiddlerPlugin]] [[EditSectionPlugin]] [[CommentsPlugin]]" > import:4>> > > :( > > That's why I keep a local repository of plugins and use <<include ... > import:4>> macros to automatically import newer versions when I update my > local archive. > > *Here's how I use STP:* > > I keep commonly used tiddlers like StyleSheets, PageTemplate, > ViewTemplate, EditTemplate, ColorPalette, reusable slider menus, help > files, formatting notes, AutoCorrectLists (for AutoCorrectPlugin), my > DisableWikiLinksList (for DisableWikiLinksPlugin), and a few other generic > tiddlers in a TW of their own. I keep a separate TW for plugins — stored > locally from sources like TiddlyTools and other places. Each time I load > one of my daily-use TWs, the IncludeList looks like this: > > <<include "SharedResources.html">> > <<include "AddOns.html" filters:"[tag[toSync]]" import:4>> > > > The first line includes all those common (non-plugin) tiddlers from the > Shared Resources store. The second imports all tiddlers tagged [[toSync]] > from my plugins TW if they are newer than the local tiddlers. (It also > prompts me to overwrite any existing tiddlers, giving me a degree of > oversight.) > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/tiddlywiki. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
