| IHelpContentProvider is never called [message #475712] |
Wed, 05 August 2009 04:58  |
Eclipse User |
|
|
|
Hi
I'm trying to add some context sensitive help to my RCP application. My
editor adapts to IContextProvider to provide the correct IContext, which
is generated on the fly.
When I open the dynamic help (F1), the "Related Topics" view is shown
correctly, but when I click one of the links, I get a HTTP error 404 from
the ProxyServlet. What I would like to see is a HTML file from another
plugin, so the URL looks like /my.plugin.id/myfile.html.
As this did not work, I wrote my own IHelpContentProducer which should
open the file and return an InputStream. I registered my class in the
plugin.xml as a contentProducer in the extension point
org.eclipse.help.contentProducer. But this does not work neither. The
method getInputStream() of my IHelpContentProducer is never called.
What am I missing here? How can I get the IHelpContentProducer working? My
target platform is Eclipse 3.5.
Thanks for any help
Roland
|
|
|
| Re: IHelpContentProvider is never called [message #479422 is a reply to message #475712] |
Mon, 10 August 2009 19:42  |
| Eclipse User |
|
|
|
Without seeing your code it's hard to tell why exactly why it is not
working. A content producer produces content only for the plug-in it is
declared in, so if you have a plug-in my.plugin which has a content
producer that content producer will be called every time the help system
sees a reference to a file in that plug-in, for example with a url of
/my.plugin/myfile.html.
Roland Brand wrote:
> Hi
>
> I'm trying to add some context sensitive help to my RCP application. My
> editor adapts to IContextProvider to provide the correct IContext, which
> is generated on the fly.
>
> When I open the dynamic help (F1), the "Related Topics" view is shown
> correctly, but when I click one of the links, I get a HTTP error 404
> from the ProxyServlet. What I would like to see is a HTML file from
> another plugin, so the URL looks like /my.plugin.id/myfile.html.
>
> As this did not work, I wrote my own IHelpContentProducer which should
> open the file and return an InputStream. I registered my class in the
> plugin.xml as a contentProducer in the extension point
> org.eclipse.help.contentProducer. But this does not work neither. The
> method getInputStream() of my IHelpContentProducer is never called.
>
> What am I missing here? How can I get the IHelpContentProducer working?
> My target platform is Eclipse 3.5.
>
> Thanks for any help
>
> Roland
>
>
>
|
|
|
| Re: IHelpContentProvider is never called [message #623517 is a reply to message #475712] |
Mon, 10 August 2009 19:42 |
| Eclipse User |
|
|
|
Without seeing your code it's hard to tell why exactly why it is not
working. A content producer produces content only for the plug-in it is
declared in, so if you have a plug-in my.plugin which has a content
producer that content producer will be called every time the help system
sees a reference to a file in that plug-in, for example with a url of
/my.plugin/myfile.html.
Roland Brand wrote:
> Hi
>
> I'm trying to add some context sensitive help to my RCP application. My
> editor adapts to IContextProvider to provide the correct IContext, which
> is generated on the fly.
>
> When I open the dynamic help (F1), the "Related Topics" view is shown
> correctly, but when I click one of the links, I get a HTTP error 404
> from the ProxyServlet. What I would like to see is a HTML file from
> another plugin, so the URL looks like /my.plugin.id/myfile.html.
>
> As this did not work, I wrote my own IHelpContentProducer which should
> open the file and return an InputStream. I registered my class in the
> plugin.xml as a contentProducer in the extension point
> org.eclipse.help.contentProducer. But this does not work neither. The
> method getInputStream() of my IHelpContentProducer is never called.
>
> What am I missing here? How can I get the IHelpContentProducer working?
> My target platform is Eclipse 3.5.
>
> Thanks for any help
>
> Roland
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03057 seconds
Home