Hi Nitin, Thanks, that's very helpful. Generally, what we are looking for is an IDE front-end because building one from scratch is obviously a lot of work. JSDT seems to fit the bill nicely. One thing we would need is to feed AST, type inferencing and code completion information from our tooling into it. I haven't seen if the current architecture supports pluggable backends like this, but I assume it shouldn't be too hard to do. The other are general UI fixes and improvements to make sure everything works nicely. I saw support for debug markers on the feature list--that's another thing we want. I don't see a counterpart of JDT's debugging UI plugin anywhere, though. Is it something that's in store until someone asks for it?
Cheers, --Vassili On Wed, Jun 3, 2009 at 10:57 AM, Nitin Dahyabhai <[email protected]> wrote: > > Vassili, > There's actually quite a bit going on, most of it currently focused on > making the fundamentals as rock solid as possible and cleaning up the UI. > Right now that means a number of low-level adjustments to the parser and > validation code to more closely reflect JavaScript's typing and syntax and > smoothing out areas of the UI that still reflect its origin as a copy of > JDT. A number of these fixes were done for 3.0.5 and 3.1 courtesy of our > newest committer, and he's already back at it for 3.2. We'll also be > tackling issues with web page integration during 3.2's development. Time > permitting, we'll be updating the existing OpenAJAX metadata support to the > newer drafts and making sure our pluggable type inferrencing engine covers > the cases our adopters have asked about. The web site documentation is > still an area we need to update, hopefully when my other 3.1 > responsibilities are finished. > > We'd love to have any contributions you're interested in making. What were > you interested in enhancing? > > Regards, > --- > Nitin Dahyabhai > Eclipse WTP Source Editing > IBM Rational > > > > *Vassili Bykov <[email protected]>* > Sent by: [email protected] > > 06/03/2009 01:30 PM > Please respond to > "General discussion of project-wide or architectural issues." < > [email protected]> > > To > [email protected] cc > Subject > [wtp-dev] JSDT status? > > > > > Hi, > > I'm starting to work on some new Javascript tooling here at Google, and > looking if there are existing open source solutions we could build on > (contributing parts back). JSDT is the obvious choice, but the "official" > information online looks old and overall it doesn't look like there's much > going on. Is anyone working on it, and how actively? > > Cheers, > > --Vassili_______________________________________________ > wtp-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/wtp-dev > > > _______________________________________________ > wtp-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/wtp-dev > >
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
