|Re: OpenAjax Metadata Support in JSDT [message #519756 is a reply to message #518376]
||Tue, 09 March 2010 20:47
| Nitin Dahyabhai
Registered: July 2009
> Based on the presentation found on this link
> ( http://www.slideshare.net/ajaxexperience2009/adam-peller-int eroperable-ajax-tools-and-mashups),
> as well as digging through the JSDT code (inside the
> org.eclipse.wst.jsdt.internal.oaametadata package), I am convinced that
> OpenAjax Metadata is kind of supported in JSDT.
> I am trying to figure out if I can use it to enable content assist of my
> to work. I could get it working partially, but as long as there is any
> namespace involved, things don't seem to work.)
That's an interesting finding that should be explored further.
Namespaces (packages?) are basically ignored in JSDT, as they don't
really exist in JS. There are bound to be a few quirks from JSDT's
heritage, however, in working with them, but these are areas we're
keen on fixing. If you can provide more detailed information in a
bug report, I'd like to pursue this further.
> I'd like to know if I can provide OAA metadata to make content assist
> work for my library. And I cannot find any information since
> documentation is pretty broken.
> Any information on that would be much appreciated.
You're not going to like this, but the answer for now is no. The
support you found was written to a two-year old draft version of the
spec, and hasn't received a lot of attention since then.
Eclipse WTP Source Editing
Eclipse WTP, IBM
Powered by FUDForum
. Page generated in 0.01722 seconds