On Dec 5, 7:33 pm, Jeremy Ruston <[email protected]> wrote: > Thanks! Over the last couple of days I've been able to get basic > wikification working (not macros, yet, though). I did see the code :) the syntax parsing looks interesting.
> > # -q, --[no-]quiet Quiet mode, do not output file > > names > > I was planning to make the default be to keep quiet unless there is an > error, and adding a verbose option for debugging. This is ok for me > > I'm especially interested in -s --subdirectories, which splits the > > tiddlers into different directories depending on there "usage" and > > creates a recipe per directory. > > OK, I wasn't sure how important that option is, and I'd be interested > to understand your use cases. ... My situation. (For other plugin devs it may be similar) ==== * Most of my plugins are stored at tiddlyspot or / and tiddlyspace. * They have been stored there with "copy / paste" and "save changes" with TW commands ** They are changed / updated with "tiddlyspot: save to web" command (broken in latest browsers) * There is no automatic system, to test and deploy them :( * There is no source/version control system to mange them ... What I want ==== * An easy way to get my plugins out of TW / tiddlyspot / tiddlyspace and use my preferred text editor and my preferred VCS. * I want to be able to create a local file "test.html" TW that only contains _one_ plugin *.js file, plus some tiddlers, needed to test the functions ** may be some shadow tiddlers are needed too. ** test.html should only contain minimum changes to a vanilla TW. * If testing is done, I want to create an "upstream.html" TW that contains all the documentation tiddlers needed to propperly present my plugins. ** There may be one or many plugins in one "presentation TW". ** There may be also 3rd party plugins in a "presentation TW". My workflow ==== My workflow and directory structure, is described at tw.plugin-dev- template space [1]. A template project is also hosted at github [2]. (I need to fix the make file, since cook parameters have been changed lately ;) If you have a look to "tests.html.recipe" and "upstream.html.reicpe" [2], you'll see, how I get "What I want" (from above). About ginsu ==== * If I want to get my plugins and documentation tiddlers out of my existing (manually controlled) "TW repos" I need ginsu. * Since some of my tiddlySpaces contain several hundred tiddlers [3] [4], it is close to impossible, to handle plugins and documentation tiddlers efficiently, if they are all in the same directory. * Creating .recipe files manully is a pain. --> That's why I'd like to have the -s --subdirectories parameter, that works similar to the ruby one. > ... I'm not super keen on the way that it > builds more specialise knowledge into the tools, but of course it > would be quite easy to add, and i'll be happy to do so. hmm... You are right. It should be kept simple. But the problem is, if you download a TiddlySpace TW it contains even more tiddlers from "system" spaces. I don't have a good idea about these plugins .... I did add an "svg" tag splitter [5] and cook option some time ago. So may be, it would be good, to have "addOns" for the new cook ... -m [1] http://dev-template-doc.tiddlyspace.com/#About [2] https://github.com/pmario/tw.plugin-dev-template [3] http://iconbuilder.tiddlyspace.com/ [4] http://freestyle-tutorial.tiddlyspace.com/ [5] https://github.com/TiddlyWiki/cooker/commit/60436f7a84c1b1adbed782ab3ebb54ee0847603d -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
