Jim, The first hurdle would be bug 298577*, since using undefined in that manner isn't currently supported. There are also parts of jQuery itself that confuse our parser, mostly having to do with regular expressions. After that, it falls down to the same 3 areas as does supporting any library: 1) Using the org.eclipse.wst.jsdt.core.inferrenceSupport extension point to add an engine to help infer Types and type information; possibly not useful in this case because jQuery doesn't document types in its source. The main use case for this is when a library documents its type information in a format other than JSDoc. 2) Using the /org.eclipse.wst.jsdt.ui.documentationProvider extension point to help find and render documentation for the JavaScript types, methods, and fields; probably not needed since jQuery doesn't have its own custom documentation format. Again, JSDoc is supported, and to a certain extent, simple line comments in the style jQuery uses. 3) Adding the necessary support for an IncludePath container, which is only useful if you're interested in providing jQuery for JavaScript development from within Eclipse plug-ins--and anyone could just as easily download it themselves and add it to their JS project.
While I don't think there's much preventing it from working, the parser changes themselves will have to wait for WTP 3.3. * https://bugs.eclipse.org/bugs/show_bug.cgi?id=298577 Regards, --- Nitin Dahyabhai Eclipse WTP Source Editing and JSDT IBM Rational _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
