On Sunday, August 25, 2013 9:50:13 PM UTC-4, Eric Shulman wrote: At present, you *CANNOT* import from remote TiddlyWikis (on a different >> domain name or a different computer on your local network). >> > > Even if this ability were possible, it would be a VERY VERY BAD THING TO > DO. That would create traffic to my site every time you open your document. >
That's a point *well* worth making. Even if there were a plugin built with this sort of thing in mind, reaching out and touching a remote TiddlyWiki every time a user loaded his local file might generate a significant amount of overhead on the repository server. If this is something Yakov ever implements, it might be appropriate to check with certain popular plugin hosts (Eric and TiddlySpace) and include some warnings/advice/etiquette for using such a feature in the real world. (It might, for example, be a good way to manually run a monthly check for updated plugins but a disaster waiting to happen to make such an include automatic on startup.) On Monday, August 26, 2013 7:48:06 AM UTC-4, Tobias Beer wrote: Great summary, Scott. > Whew. Brevity isn't my strong suit when I'm in a rush, so that's good to hear! :P > So, do I understand right that including plugins and having them run > without being saved in the TiddlyWiki is not quite an option... because it > may fail with some plugins? > I *think* I've run across plugins where it fails (or is only partially successful) — but in posting last night, I couldn't think of a specific example, but I'd be reluctant to load all plugins via include rather than having them present native in my TiddlyWikis. Yakov has this to say about how included evaluated plugins are different from those launched natively: - Plugins are not registered (no entries in the backstage). - There are no dedicated reactions on errors. - There's no check preventing some plugin from launching twice or more. ... which fits with my rule-of-them to use <<include ... eval>> only with plugins that have simple, specific macro calls. Ok, so whenever you add something to your plugin repo and then open one of > your individual wikis you get notification prompts by SharedTiddlersPlugin > when it wants to overwrite already present tiddlers. > That depends on the import mode you use. My preference is for "import:4," but here's Yakov's description of all four import modes: - 1 means "import anyway, even if a tiddler with such name is present" (useful, for instance, as a silent mode for updating plugins). - 2 means "skip import if a version of this tiddler in the main store has a *modified* date no less than the one being imported" (i.e., only import newer tiddlers). - 3 means "import only with confirmation from the user." - 4 combines the requirements of modes 2 and 3 — say, for autoupdating plugins from a central TiddlyWiki while allowing the user total control over import decisions. > I wonder why you are using a [[toSync]] tag, though. Why not just include > all tagged [[systemConfig]] and have SharedTiddlersPlugin create those that > are new and ignore those that already exist AND are unchanged compared to > the source. Is the latter not an option for SharedTiddlersPlugin? Because > it really should be. Then you'd automatically only ever import new stuff > when it's actually there. > You've got it. With import mode 2 or 4, that's exactly how importing works. As for the [[toSync]] tag, it's down to personal usage. I have many plugins installed and enabled in my add-ons repository that I don't want running in each and every TiddlyWiki. Having the [[toSync]] tag allows me to be selective with ease. (If I wanted all my plugins in all my TiddlyWikis, though, I'd do exactly what you suggest: <<include "AddOns.html" filters:"[tag[systemConfig]]" import:4>>) -- 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.
