Re: Next steps for Caja-CapTP

On Oct 11, 2009, at 21:40, [email protected] wrote:

> a. Remove the dependency on E-on-Java and E-on-JS, resulting in a pure
> Cajita project. (The Caja-CapTP tests are currently written in Updoc
> format. We can refactor directly to jsUnit-style tests, or consider
> Mike Samuel's JSDoc tool that gives Updoc-like functionality.)


It is a design goal of Caja-CapTP to eventually interoperate with  
other CapTP implementations, of course including the 'normal' E-based  
implementations.

I wish that the test suite in Caja-CapTP continue to parallel as  
closely as possible the test suite for CapTP-in-E (which currently  
exists as a component of E-on-CL), from which it was derived, so that  
improvements to tests (which are greatly needed on both sides) may be  
shared.

I will not support any changes which will remove opportunities to  
avoid duplicated effort in the future. We are in general desperately  
short of available time from interested programmers.


1. Why do you wish to remove these dependencies?

    1a. If because E-on-Java is awkward to install, would the existence
        of a simple installer for Unix-style operating systems, and
        perhaps other changes to make things more pleasant, resolve  
this?

2. Would removing E-on-JavaScript's dependency on E-on-Java, such that
    it was a pure-JS or possibly even pure-Cajita (maybe with some Java)
    system, suffice? (The necessary work here would be providing a  
parser
    for E written in JavaScript, perhaps by way of OMeta.)

3. Would revising the test suite such that, while still using the Updoc
    syntax for tests, the test code itself is Cajita, suffice?

-- 
Kevin Reid                                  <http://switchb.org/kpreid/>