Hi TheDiveO On Mon, Sep 1, 2014 at 2:25 PM, TheDiveO <[email protected]> wrote:
> *Nota bene:* I've seen that Jeremy has just published the example plugin > repository. I'm well aware of it, it's fine ... yet I want to work in a > slightly different, more integrated plugin development cycle where I mainly > use "TW5 in da browsa" but without the existing pluginmaker.js > functionality. The rationale is that I want to develop and publish small, > self-contained plugins where each plugin gets its own repository and where > all plugin files are always under source control in the normal tiddler file > tree. In particular, I want to avoid having tiddler sources in both > *tiddlers/* as well as *plugins/*. > Why do you want to avoid having tiddlers in both tiddlers/ and plugins/? That is the way that TiddlyWiki5 is designed to work. What is it that you want to be able to do in the browser but can't with the repo layout I published? > My idea now is to implement a new command "--makeplugin" that is the > Node.js variant of pluginmaker.js; yet with an important difference: it > doesn't delete the plugin non-shadow tiddlers as they get into the package > as shadows. For instance, to create a plugin I would use these commands: > > --makeplugin "$:/plugins/TDO/example" > "[field:title/\$:\/plugins\/TDO\/example\//]" > --savetiddler "$:/plugins/TDO/example" "example.tid" > Possibly simpler to use the `prefix` filter operator: --makeplugin "$:/plugins/TDO/example" "[prefix[$:/plugins/TDO/example/]]" > > 1. This would first start a headless TW5, read in the TiddlyWiki that > contains all the sources. > 2. Next, it would pack the plugin on the basis of a filter expression > specified to the --makeplugin command. > - Something that isn't clear to me: as the makeplugin command would > change the plugin tiddler text, would the headless TW5 instance try to > sync > it back to disk? I would assume that it can't do this as long as I'm > making > sure I'm using a wiki edition without sync adaptor loaded. Correct? > > That's right, syncing to disc only happens if the filesystemadaptor plugin is loaded. > > 1. Then I just save the plugin tiddler to file system so I can later > upload it and also copy it to a wiki edition for official deployment. > > I would like to get feedback on this idea. Anything terribly wrong with it? > It feels like swimming against the current; I don't fully understand what's wrong with the recommended approach? Best wishes Jeremy > > Best regards, > TheDiveO > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" 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/tiddlywikidev. > For more options, visit https://groups.google.com/d/optout. > -- Jeremy Ruston mailto:[email protected] -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
