| Content assist contributor extension points? [message #36403] |
Fri, 20 March 2009 09:59  |
Eclipse User |
|
|
|
Originally posted by: clemens.froglogic.com
Hello.
I am wondering if DLTK offers extension points for additional content
assist contributors the way JDT and CDT do?
(For example in case of a JavaScript project one might want to offer
completion for Microsoft APIs or custom APIs which aren't supported out
of the box by the DLTK-JavaScript IDE.)
With best regards
Clemens Anhuth
--
www.froglogic.com - Squish - Multi-Platform GUI Testing
|
|
|
| Re: Content assist contributor extension points? [message #36467 is a reply to message #36403] |
Fri, 20 March 2009 15:57  |
|
Clemens Anhuth wrote:
> I am wondering if DLTK offers extension points for additional content
> assist contributors the way JDT and CDT do?
>
> (For example in case of a JavaScript project one might want to offer
> completion for Microsoft APIs or custom APIs which aren't supported out
> of the box by the DLTK-JavaScript IDE.)
It *is* supported by WTP's JSDT, on the other hand, through its
org.eclipse.wst.jsdt.ui.javaCompletionProposalComputer extension
point. But it sounds more like you should plug into the indexing so
that the files declaring those APIs are content assistable and
resolvable like everything else.
--
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
_
Nitin Dahyabhai
Eclipse Web Tools Platform
|
|
|
| Re: Content assist contributor extension points? [message #36481 is a reply to message #36467] |
Fri, 20 March 2009 16:16 |
| Eclipse User |
|
|
|
Originally posted by: clemens.froglogic.com
Nitin Dahyabhai wrote:
> Clemens Anhuth wrote:
>> I am wondering if DLTK offers extension points for additional content
>> assist contributors the way JDT and CDT do?
>>
>> (For example in case of a JavaScript project one might want to offer
>> completion for Microsoft APIs or custom APIs which aren't supported
>> out of the box by the DLTK-JavaScript IDE.)
>
> It *is* supported by WTP's JSDT, on the other hand, through its
> org.eclipse.wst.jsdt.ui.javaCompletionProposalComputer extension point.
> But it sounds more like you should plug into the indexing so that the
> files declaring those APIs are content assistable and resolvable like
> everything else.
>
Hello Nitin,
Unfortunately in the case I am dealing with the problem is that there
are no source code files in the scripting language at hand declaring the
APIs. (I suspect it is similar with MS JScript APIs usable in WSH,
JavaScript APIs in Adobe products, etc.)
With best regards
Clemens Anhuth
|
|
|
Powered by
FUDForum. Page generated in 0.02666 seconds
] 
Search
Help
Register
Login
Home
