One of my drivers is that I want the new build tool to be able to work as an HTTP server as well as spitting out files to the file system. This is so that one can edit a raw JS file in a text editor and then flip to the browser and refresh in order to see the results, without an explicit manual build step. I think that's what you're asking for, too, isn't it?
I'm intending to use the existing recipe file format as the starting point so that it's possible to do byte-for-byte comparisons between the old toolchain and the new. Later on, when we get to updating TiddlyWiki itself, I would hope to bring in a module system compatible with common.js, as you suggest. Best wishes Jeremy On Mon, Nov 14, 2011 at 10:33 AM, tiddlygrp <[email protected]> wrote: > Hi, > > recently Jeremy told about changing the current build system of tw in > ruby to a system based on node.js. A suggestion is to NOT to depend > on node.js, but allow a build system that also can be used in a > browser. An example is require.js or one of the many similar > systems. Their main advantage is that tw can be developed in small > files and directly used in this form without explicit "cooking". For > a release these tools will cook up an integrated version. What do you > think about that? > > -- > 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. > > -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- 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.
