Hi Mat For instance, in a school setting, the administrator might set up a TW >> plugin library that contains course materials. By dragging and dropping a >> single tiddler, individuals can then connect to that library and import its >> resources. >> > > Hm, extremely interesting. Does this mean vanilla TW5 can do what I > believe otherwise only the node.js version can do, i.e to > momentarily/session-wise import tiddlers? Or maybe we are talking about the > node.js version to begin with? >
Here we're talking about importing a plugin from the plugin library; there's nothing momentary about it, it permanently copies the tiddler from the library to the wiki. The plugin library is entirely browser based. > Ah, great! Is it correct that we currently do not have a simple way to > bundle up arbitrary tiddlers into a plugin? > It's simple enough under Node.js. The process in the browser is bit intricate because there's no user interface; it has to be done from the browser developer console > Also... and I'm digressing here but: I'm investigating the terminology > we're using for things in TW. Is "plugin" a carefully picked term here or > really of more spontaneous origin? The thing is, I'm beginning to be > concerned that the eventual Federation will need a very strict and > carefully chosen terminology to minimize confusion because I expect the > Federation to be a boost for community growth attracting people with niche > interests that are not as interested in TW per se but more in a particular > Application for TW (e.g "authoring books" or "course material management") > or particular Content (e.g "folk music", "Harry Potter",...). In other > words, I think sub-communities will form and for, particularly, such > "Application Communities", then we had better use a well defined lingo so > to minimize confusion in the interaction. I may sound overly optimistic in > this but I believe TW will be very big one day and nomenclature matters had > better be straightened out before this day. > > So, again, is "plugin" - as opposed to "addon" (add-on?), "extension", > "bundle" and other terminology the best term for our case here? I'm in no > way implying that it is not, I'm merely > I think "plugin", "add-on" and "extension" are all synonyms. I chose the word "plugin" because I think it's the strongest word; it describes the mechanism, while "add-on" and 'extension" are more about what the mechanism accomplishes. "Plugin" is also in very common usage, and I wanted to exploit users existing understanding of the "plugin" concept. I don't think that the word "plugin" is suitable for talking about the payload of federation. We'll probably need to adopt/evolve a new vocabulary for federation. Best wishes Jeremy. > asking. > > Thank you again Jeremy > > <:-) > -- Jeremy Ruston mailto:[email protected] -- 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/CAPKKYJZwGAJjXHxociExu680e0Hh7ZpAByoDxfa4ONAycxguBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
