On Aug 11, 2009, at 22:01, Kris Kowal wrote:
On Tue, Aug 11, 2009 at 1:33 PM, Mike Stay<[email protected]> wrote:
Cool! We'll check it out.
I will no doubt be a man in search of a distraction this weekend. Who
do I have to bribe to make a branch of caja and caja-captp for the
purpose of researching Narwhal packaging? Do you have continuous
integration? Is there a system that could be harnessed to post a
package.zip and package.json file somewhere predictable periodically?
Kris Kowal
Caja-CapTP is only just started and has nothing setup for releases or
automatic testing. (The tests currently only run in a browser, anyway,
because the Updoc framework assumes a HTML document/DOM; I need to fix
this but it's not on the GSoC-activities timeline so won't happen in
the next two weeks.)
If you'd like to work on a branch I can add you to the project and we
can make a branch. I'd certainly appreciate any help with server-JS
matters. Why not, though, check out the code[1] and play with it and
see how much needs to be done? You can always switch to a newly
created branch.
I don't know anything about what the requirements of Narwhal
packaging are yet. However, Caja-CapTP *is* supposed to run on both
browsers and servers, so it does need something like this.
Note that all Caja-CapTP code is cajoled and packed into a single Caja
module. Caja-CapTP will *NOT* run without the Cajita runtime. (It does
not deliberately depend on anything specific to web browsers, however.)
[1] svn checkout http://caja-captp.googlecode.com/svn/trunk/ caja-captp
--
Kevin Reid <http://switchb.org/kpreid/>
