| Unwanted Contributions [message #125484] |
Tue, 03 February 2009 12:31  |
Eclipse User |
|
|
|
I have a fairly general question, but I've done quite a bit of searching and
have reached a conclusion that seems dubious, so hopefully somebody can
simplify this for me.
I develop an internal RCP app, and we are refactoring it so that it has a
generic framework that can be easily extended for new applications. I've
been having trouble with getting a lot of unwanted contributions to the UI.
For unwanted action sets, I've been using IWorkbenchPage.hideActionSet(),
and now I'm trying to use xslt transformations to get rid of help
contributions from org.eclipse.platform.doc.user, and am having great
difficulty. It seems unreasonable that plugin users are required to do such
low-level processing to hide things unrelated to their applications. Could
there be something I'm doing wrong in my project setup or plugin
specification or something else that's causing this? Is there a smooth way
to avoid these things? I've searched high and low for a solution to these
problems, but haven't really found an answer that doesn't take for granted
that your applications will have all these features meant for the eclipse
ide unless you go out of your way to stop them.
Thanks!
Nick
|
|
|
| Re: Unwanted Contributions [message #125501 is a reply to message #125484] |
Tue, 03 February 2009 13:38  |
| Eclipse User |
|
|
|
Never mind, I think I have a good handle on what I was doing wrong in
general.
"Nick Beary" <NBeary@express-scripts.com> wrote in message
news:gm9v1v$6va$1@build.eclipse.org...
>I have a fairly general question, but I've done quite a bit of searching
>and have reached a conclusion that seems dubious, so hopefully somebody can
>simplify this for me.
>
> I develop an internal RCP app, and we are refactoring it so that it has a
> generic framework that can be easily extended for new applications. I've
> been having trouble with getting a lot of unwanted contributions to the
> UI. For unwanted action sets, I've been using
> IWorkbenchPage.hideActionSet(), and now I'm trying to use xslt
> transformations to get rid of help contributions from
> org.eclipse.platform.doc.user, and am having great difficulty. It seems
> unreasonable that plugin users are required to do such low-level
> processing to hide things unrelated to their applications. Could there be
> something I'm doing wrong in my project setup or plugin specification or
> something else that's causing this? Is there a smooth way to avoid these
> things? I've searched high and low for a solution to these problems, but
> haven't really found an answer that doesn't take for granted that your
> applications will have all these features meant for the eclipse ide unless
> you go out of your way to stop them.
>
> Thanks!
>
> Nick
>
|
|
|
Powered by
FUDForum. Page generated in 0.24883 seconds
Home