[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-29 Thread Tobias Beer
Thanks for the heads up ;-) -- 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 tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-28 Thread Yakov
вторник, 27 августа 2013 г., 23:22:15 UTC+4 пользователь Tobias Beer написал: Hi Yakov, It would be really great if you could wrap up a sample setup, comment it, zip it and dropbox it. Otherwise it's all just in my head and about as quickly gone. It's just, the complexity of it would be

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-27 Thread Yakov
Hello gentlemen, as Scott have already pointed most of the technical stuff, I'd like to add a couple of pragmatic tips: 1. eval vs import for plugins: I personally use eval for some plugins that are 1) editor tools and not necessary to read content 2) can be device-dependent example 1:

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-27 Thread Tobias Beer
Hi Yakov, It would be really great if you could wrap up a sample setup, comment it, zip it and dropbox it. Otherwise it's all just in my head and about as quickly gone. It's just, the complexity of it would be much smaller when I could *see* it in action. *Click here*, *see here*, done. Less

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-26 Thread Tobias Beer
Great summary, Scott. 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? Ok, so whenever you add something to your plugin repo and then open one of your individual wikis

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-26 Thread Tobias Beer
Thanks, again Scott, very insightful stuff here. 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

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-25 Thread Scott Simmons
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

Re: [tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-25 Thread David Bakin
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 goo...@secret-hq.com wrote: Hi, David — As a fan of SharedTiddlersPlugin, here's what I've observed: INCLUDE on its own makes specified tiddlers from

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-25 Thread Scott Simmons
A bit scatterbrained today. I forgot to explain filters:[tag[toSync]]: Some plugins I want to keep up to date in all my TiddlyWikis. I tag these [[toSync]] in AddOns.html and use this macro call in the IncludeList of my other TWs: include AddOns.html filters:[tag[toSync]] import:4 ... to

[tw] Re: SharedTiddlersPlugin and plugins: import, include with eval, or both?

2013-08-25 Thread Eric Shulman
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]]