Hi Tobias Thanks for your patience with the discussion, it’s useful and interesting!
> 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>. It was probably a mistake to continue to use the word “bundle” in this thread. For clarity, I was using the term to describe a JSON file containing a number of tiddlers. > 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. OK, so what’s wrong with using a field like “plugin-type” to indicate that the special behaviour of unpacking shadow tiddlers should take place? > 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. What do you mean by “special treatment”? Plugins (where `plugin-type` is “plugin”) have no special behaviour in the wiki store beyond the unpacking of shadow tiddlers. Features like the plugin listing in the control panel aren’t intrinsic to the plugin mechanism; they’re just tiddlers in the control panel. What special treatment do you think plugins are subject to that you’d like to avoid? > 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. Now that you’re bring even more of the behaviour of plugins to your “bundles” I’m really failing to see the difference between a bundle and a plugin. Surely you are just re-inventing plugins? > 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. But you are saying that the plugin mechanism isn’t suitable for the purpose you have in mind, and yet as a replacement you are suggesting adding all the features of plugins to JSON tiddlers. > 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… But that is exactly what plugins are for! Again and again you are saying that something else is needed and yet you are just describing the existing behaviour of plugins. Best wishes Jeremy. > > Best wishes, > > — tb > > -- > 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] > <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/64F1FD76-382B-4594-B7D0-C3C09648FCD9%40gmail.com. For more options, visit https://groups.google.com/d/optout.
