Hey guys, Me again. I have been having way too much fun with this for my own good.
It sounds like « plugout » introduces a new term and would be too confusing. So I will go back to plugin soon. I have a demo site up here: http://tiddlywiki.howwownow.com/ Most importantly, the draggle plugin is available here: http://tiddlywiki.howwownow.com/#%24%3A%2Fplugins%2Fchris2fr%2Fasplugout The Tiddly site also serves as a demo site. You can [Export All] -> [TiddlyWiki as Plugout (.tid)] and import that anywhere as a plugin. It is non-intrusive, mostly. Feel free to play with the « Plugout » SideBar as well. Perhaps a better name would be TiddlyShadow. I like thinking about names. Christopher Mann > Le 10 nov. 2015 à 18:02, Tobias Beer <[email protected]> a écrit : > > Hi Jeremy, > > I think there’s a lot of confusion here. The core has two features: > > * “plugins”, which require a type, and can optionally have a version. They > contain shadow tiddlers that are switched in when the plugin is loaded > * “bundles”, as we’re referring to JSON files containing a bundle of tiddlers > that can be exported or imported as a single unit > > Possibly, there is some mixing up in terms of ...terms. So far, I have not > recognized the term "bundle" as part of the core lingo... which is more or > less confirmed by searching for it on TiddlyWiki.com. Of course, I knew > plugins that are actually introduced as "bundles of tiddlers > <http://tiddlywiki.com/#PluginMechanism>" and of JSON > <http://tiddlywiki.com/#JSONTiddlers> tiddlers introduced as data tiddlers > <http://tiddlywiki.com/#JSONTiddlers>. > > Whatever I was referring to as "bundle" indeed is located in the middle, > feature- / constraint-wise. > > I think you’re asking for “bundles” to behave like plugins, but for them to > somehow not become plugins in the process. That’s the crux of what I’m not > understanding. > > Is it just the requirement for a “plugin-type” field? You must see that an > indicator other than “type:application/json” is needed; otherwise the system > would attempt to load all data tiddlers as plugins. > > I can see where the confusion was coming from. Certainly, the kind of > "bundles" I was referring to were by design of type:application/json, at > least in terms of format, which means that they would need to be more than > just plain json data tiddlers in order to work the shadow magic, as we don't > unpack those the shadow tiddler way. > > Introducing another type of tiddler may be a shortcut to actually reducing > confusion and to separate whatever such a "bundle" could be called from > plugins. The kind of "simple bundle" I had in mind being defined as: > having the structure of plain json data tiddlers > implementing the shadow mechanism of plugins > ...and that's it. So, unlike "plugins", "themes", or "languages" they would > have no special treatment, except, any plugins contained in such a "bundle" > would be loaded as plugins, in other words, a plugin in a plugin. Whether > such a construct would be called "bundle" is not so much of importance as the > desire for that to exist. Clearly, plugins are more than just that / require > more than the above to get going. > > But yes, like current plugins, one may want a central spot to look at > "bundles". So, it would be wise to have them be of a plugin-type:bundle (or > any other name) and then show them in a corresponding tab under ControlPanel > > Plugins > Bundles. > > You seem to think that there are vague, unexpected restrictions on how > plugins are formed, but I don’t really understand what you’re getting at. > > Not at all. My suggestions were in no way intended as criticism. Instead, I > was wondering how to arrive at the above model+behavior. > > A plugin is a JSON tiddler with the additional field “plugin-type" > appropriate content and the shadows packed into the body. How much simpler > could it be? > > I would be all fine to introduce plugin-type:bundle, which would loosen up on > any requirements that go beyond 1. and 2. above and treat such a bundle as if > a regular tiddler, especially upon import, except for the shadow magic. > > Bundles could serve a wide range of purposes: > > * app setups > * complex themes > * user preferences > * content bundles, e.g. "help" > * etc... > > Best wishes, > > — tb > > -- > You received this message because you are subscribed to a topic in the Google > Groups "TiddlyWiki" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/tiddlywiki/HrL5owEOJKM/unsubscribe > <https://groups.google.com/d/topic/tiddlywiki/HrL5owEOJKM/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/group/tiddlywiki > <http://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/533fcff5-b41b-4801-84d4-ac055362a5a4%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/533fcff5-b41b-4801-84d4-ac055362a5a4%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/F25F0C29-B6A8-4CCE-A045-008962436EDA%40mann.fr. For more options, visit https://groups.google.com/d/optout.
