Hi, reply inline.
On Nov 14, 1:51 pm, Jeremy Ruston <[email protected]> wrote: > 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? Yes, for the editing part. But with using require.js you need no server! you can also browse file:// based url's and all needed tw parts are loaded on demand. That's the great advantage. Later for deployment require.js can cook up your "integrated" tw. > > 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. that is alas not possible easily > > 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. > That is a nice long term goal, but not my primary concern. My primary idea is to use and develop tw serverless by doing everything in the browser directly. > Best wishes > > Jeremy -- 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.
