| How-to extend JDT Package Explorer View for a new plugin [message #95432] |
Wed, 16 July 2003 22:58  |
Eclipse User |
|
|
|
I am in the process of writing a new plugin and I have a question about
how I should structure my plugin. It seems that the only way I can
implement my own domain model is to write my own view. However, what I
would like to do is some how extend the Package Exploer view and implement
my model, menus, actions, and wizards. The reason I would like to do this
is so the user has access to all of Package Explorer view as well as my
plugin. Tons of code has been written for this view and I do not want to
duplicate it if possible. Is there a way I can do this?
|
|
|
|
|
|
| Re: How-to extend JDT Package Explorer View for a new plugin [message #96191 is a reply to message #96045] |
Fri, 18 July 2003 02:27  |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Henry Tafolla wrote:
>Daniel Megert wrote:
>
>
>
>>Henry Tafolla wrote:
>>
>>
>
>
>
>>>I am in the process of writing a new plugin and I have a question about
>>>how I should structure my plugin. It seems that the only way I can
>>>implement my own domain model is to write my own view.
>>>
>>>
>>>
>>Yes, if it should show more than just resources and/or Java elements.
>>There is currently a proposed item on the 3.0 plan which is targeted at
>>your needs: General Purpose Navigator.
>>
>>
>
>
>
>>>However, what I
>>>would like to do is some how extend the Package Exploer view and implement
>>>my model, menus, actions, and wizards. The reason I would like to do this
>>>is so the user has access to all of Package Explorer view as well as my
>>>plugin. Tons of code has been written for this view and I do not want to
>>>duplicate it if possible. Is there a way I can do this?
>>>
>>>
>>>
>>You can
>>- use all the public API components which the Package Explorer itself uses
>>- contribute your filters to the Package Explorer
>>- adapt your model elements to Java elements or resources to let them
>>show up in the Package Explorer
>>
>>
>
>
>
>>HTH
>>Dani
>>
>>
>
>Daniel,
> I appreciate your response. Are there any examples that I can
>reference? I am new to developing with the Eclipse platform. To address
>your first bullet would I create my own view and then extend the
>PackageExplorerPart view
>
No, you should not extend it since it is internal and can change at any
time. But yes, create your own view.
> or just contribute my plugin to the Package
>Explorer in the plugin.xml.
>
Parts are contributed by a plug-in and not the other way around. Since
you have your own model elements you probably aready have a plug-in. You
can create a your own "Navigator" in your plug-in. Eventually you may
want to separate UI and model into different plug-ins.
>To address you last bullet how would I go
>about adapting my model to Java elements or resources.
>
See IAdaptable interface and for example code have a look at the adpter
factories in JDT UI plug-in.
HTH
Dani
> I have read allot
>of the articles online but none seem to address these types of questions.
>
>Thank You,
>Henry
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03662 seconds
Home