Eclipse Community Forums: GMF (Graphical Modeling Framework) » Custom Tabbed Properties Contribution declarations (through code instead of in the plugin.xml) ?

Home » Modeling » GMF (Graphical Modeling Framework) » Custom Tabbed Properties Contribution declarations (through code instead of in the plugin.xml) ?

Custom Tabbed Properties Contribution declarations (through code instead of in the plugin.xml) ? [message #18214]

Mon, 14 August 2006 21:55

Eclipse User

Originally posted by: khai.n.situvista.com

I'm not sure if this is still the appropriate group to ask questions
about the tabbed properties contribution so please re-direct me if this
should be asked somewhere else.

I have a model that has a large tree structure for its properties. I
have a MultiPageEditor where one of the pages hosts this tree in a
TreeViewer (other pages host diagrams). When the user click on a node
in this tree I need to display a set of appropriate tabs and
corresponding sections for that node in the Properties View.

I already know how to declare all the extension points and implement the
correct interfaces for this to work but the effort is becoming a little
daunting; there are too many types of nodes and there are
proportionately many more permutations of tabs and sections to define
and maintain manually in the plugin.xml.

I would like to implement a factory in code and dynamically declare
these extensions instead of manually declaring them in the plugin.xml.

I've browsed through
org.eclipse.ui.internal.views.properties.tabbed.view.TabbedP ropertyRegistryFactory
and corresponding classes and these might have the functionality I
need... but they are marked as 'internal'

Q1. Am I on the right track? And is there a hint towards 'best
practices' in working with these classes?

My userbase is pretty committed to the official 3.2 release for at least
until 3.3 is officially out so I'm not worried about using 'internal'
classes and having to refactor/migrate for any incremental updates until
then.

Thanks for any help on this!!!

-- Khai --

Re: Custom Tabbed Properties Contribution declarations (through code instead of in the plugin.xml) ? [message #20808 is a reply to message #18214]

Wed, 16 August 2006 11:18

Eclipse User

Hi Khai,

The tabbed properties view can only be contributed to through the extension
points in plugin.xml.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=131855 for a feature
request for dynamic support.

Cheers...
Anthony

"Khai M Nguyen" <khai.n@situvista.com> wrote in message
news:ebr9i9$boi$1@utils.eclipse.org...
> I'm not sure if this is still the appropriate group to ask questions about
> the tabbed properties contribution so please re-direct me if this should
> be asked somewhere else.
>
> I have a model that has a large tree structure for its properties. I have
> a MultiPageEditor where one of the pages hosts this tree in a TreeViewer
> (other pages host diagrams). When the user click on a node in this tree I
> need to display a set of appropriate tabs and corresponding sections for
> that node in the Properties View.
>
> I already know how to declare all the extension points and implement the
> correct interfaces for this to work but the effort is becoming a little
> daunting; there are too many types of nodes and there are proportionately
> many more permutations of tabs and sections to define and maintain
> manually in the plugin.xml.
>
> I would like to implement a factory in code and dynamically declare these
> extensions instead of manually declaring them in the plugin.xml.
>
>
> I've browsed through
> org.eclipse.ui.internal.views.properties.tabbed.view.TabbedP ropertyRegistryFactory
> and corresponding classes and these might have the functionality I need...
> but they are marked as 'internal'
>
> Q1. Am I on the right track? And is there a hint towards 'best practices'
> in working with these classes?
>
>
>
> My userbase is pretty committed to the official 3.2 release for at least
> until 3.3 is officially out so I'm not worried about using 'internal'
> classes and having to refactor/migrate for any incremental updates until
> then.
>
>
>
> Thanks for any help on this!!!
>
> -- Khai --

Re: Custom Tabbed Properties Contribution declarations (through code instead of in the plugin.xml) ? [message #21681 is a reply to message #20808]

Wed, 16 August 2006 19:41

Eclipse User

Originally posted by: khai.n.situvista.com

Thanks Anthony.

-- Khai --

Anthony Hunter wrote:
> Hi Khai,
>
> The tabbed properties view can only be contributed to through the extension
> points in plugin.xml.
>
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=131855 for a feature
> request for dynamic support.
>
> Cheers...
> Anthony
>
> "Khai M Nguyen" <khai.n@situvista.com> wrote in message
> news:ebr9i9$boi$1@utils.eclipse.org...
>> I'm not sure if this is still the appropriate group to ask questions about
>> the tabbed properties contribution so please re-direct me if this should
>> be asked somewhere else.
>>
>> I have a model that has a large tree structure for its properties. I have
>> a MultiPageEditor where one of the pages hosts this tree in a TreeViewer
>> (other pages host diagrams). When the user click on a node in this tree I
>> need to display a set of appropriate tabs and corresponding sections for
>> that node in the Properties View.
>>
>> I already know how to declare all the extension points and implement the
>> correct interfaces for this to work but the effort is becoming a little
>> daunting; there are too many types of nodes and there are proportionately
>> many more permutations of tabs and sections to define and maintain
>> manually in the plugin.xml.
>>
>> I would like to implement a factory in code and dynamically declare these
>> extensions instead of manually declaring them in the plugin.xml.
>>
>>
>> I've browsed through
>> org.eclipse.ui.internal.views.properties.tabbed.view.TabbedP ropertyRegistryFactory
>> and corresponding classes and these might have the functionality I need...
>> but they are marked as 'internal'
>>
>> Q1. Am I on the right track? And is there a hint towards 'best practices'
>> in working with these classes?
>>
>>
>>
>> My userbase is pretty committed to the official 3.2 release for at least
>> until 3.3 is officially out so I'm not worried about using 'internal'
>> classes and having to refactor/migrate for any incremental updates until
>> then.
>>
>>
>>
>> Thanks for any help on this!!!
>>
>> -- Khai --
>
>

Previous Topic:	Still not solved: Semantical container != Graphical container
Next Topic:	Adding "underline" and "strikethrough" in appereance

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 09:27:29 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter