|
Re: Content Assist exstension in JSP editor [message #529597 is a reply to message #529375] |
Mon, 26 April 2010 14:01 |
|
Filip,
You are correct, there have been significant improvements made to the content assist and the extension points adopters can use to extend it.
Assuming you have one of the latest WTP 3.2 milestone builds I suggest you take a look at the org.eclipse.wst.sse.ui.completionProposal extension point in the org.eclipse.wst.see.ui plugin. It is very well documented and provides examples. If you are still having issues after reading through the documentation please let me know and I will help in any way I can.
Blue Skies,
~Ian
Ian Tewksbury
WTP JavaScript Tools
IBM Rational
-----
“When once you have tasted flight, you will forever walk the earth with your eyes turned skyward, for there you have been, and there you will always long to return.” ~Leonardo da Vinci
|
|
|
|
Re: Content Assist exstension in JSP editor [message #529880 is a reply to message #529859] |
Tue, 27 April 2010 14:39 |
|
Filip Kis wrote on Tue, 27 April 2010 09:41 | However I've found that i would greatly benefit if I would be able to extend
org.eclipse.wst.xml.ui.internal.contentassist.AbstractXMLCom pletionProposalComputer
since I'm basically dealing with content assisting of attribute values. But the usage of that class is discouraged (since it's internal). Is there any way around this, because I don't feel like reimplementing the whole XML parsing logic.
| There was consideration made as to whether or not to make that class API when the new framework was built but we did not think there would be demand for it and in an effort to keep the public API small we opted to make it internal. If it is something you feel would be usefull to the community as a whole please open a Bugzilla enhancement request with votes and if there is enough demand for access to it we could work on making it API quality.
Filip Kis wrote on Tue, 27 April 2010 09:41 | Also, I'm doing this for a JSP Tag library and it would be great if I could access the taglib declarations (to know the prefix of my taglib) and maybe some other information (that didn't come to my mind yet). So any tip on how I could access this information in my content assist class would be helpful.
| All of the taglib code is also internal. You could take a look at the internal JSPTaglibCompletionProposalComputer to see how we generate suggestions based on taglibs. If the Taglib code is something you think would be useful API, you could open another enhancement request for that as well, noting which classes/methods would be useful to be API and why.
If you do open the enhancements please report their numbers back here for documentation purposes.
Blue Skies,
~Ian
Ian Tewksbury
WTP JavaScript Tools
IBM Rational
-----
“When once you have tasted flight, you will forever walk the earth with your eyes turned skyward, for there you have been, and there you will always long to return.” ~Leonardo da Vinci
|
|
|
Powered by
FUDForum. Page generated in 0.04774 seconds