Vassil, JSDT's JDT ancestry allows for anyone to supply a completion "computer" by extension point (org.eclipse.wst.jsdt.ui.javaCompletionProposalComputer), and provides mechanisms for accessing and modifying our AST (it mirrors the JDT constructs, but is too much to detail here). The inferencing engine has an feature request, 242162, for opening it up further in 3.2. Since its results are already merged into the model, the larger question is whether it's open enough to achieve what adopters are asking of it, and for that we need more feedback from people trying to work with it. General UI fixes would be pretty nice to have contributions on, since we're already looking at those changes in the next release (an RSS feed of a bugs fixed in WTP Bugzilla query can be handy if you want to monitor progress). Now is an excellent time to dive in.
As for debugging support, that functionality was intended to remain with the ATF incubating project when JSDT was graduated into the Web Tools Platform for 3.0. It's certainly not something we were planning to attempt with JSDT in time for WTP 3.2. A second continuation review is planned to keep the ATF project alive (see http://dev.eclipse.org/blogs/wayne/2009/05/20/atf-termination-review-deferred/ ), and I'm sure the PDT team would welcome a helping hand in their efforts. Regards, --- Nitin Dahyabhai Eclipse WTP Source Editing IBM Rational Vassili Bykov <[email protected]> Sent by: [email protected] 06/04/2009 05:23 PM Please respond to "General discussion of project-wide or architectural issues." <[email protected]> To "General discussion of project-wide or architectural issues." <[email protected]> cc Subject Re: [wtp-dev] JSDT status? 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
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
