| Tab Property Pages are internal?? [message #147600] |
Thu, 17 November 2005 22:49  |
Eclipse User |
|
|
|
Originally posted by: bob.donovan.ugs.com
Hi,
I like the way that WebTools have provided the cool Tab Properties Pages.
I would like to utilize this in my work.
Looking at the extension points described in
org.eclipse.wst.common.ui.properties, the "propertySections" extension
says that I have to implement the "IPropertySection" interface. I couldn't
find this class, so I looked at the GMF example that use this. It looks
like the interface is "ISection".
But I noticed that ISection is "internal" found at
org.eclipse.wst.common.ui.properties.internal.provisional
Typically this means we should not use this class and therfore even the
extension point.
* Can someone tell me if it is safe to use this extension point?
* Are there plans to make it public?
* The fact that this is internal may mean that we should not be extending
it. Should we stay away from this functionality?
Thanks
|
|
|
| Re: Tab Property Pages are internal?? [message #147640 is a reply to message #147600] |
Fri, 18 November 2005 01:48  |
 David Williams
Messages: 722
Registered: July 2009 |
Senior Member |
|
|
On Thu, 17 Nov 2005 17:49:39 -0500, Bob Donovan <bob.donovan@ugs.com> wr=
ote:
> Typically this means we should not use this class and therfore even th=
e extension point.
>* Can someone tell me if it is safe to use this extension point? * Are =
there plans to make it public?
> * The fact that this is internal may mean that we should not be extend=
ing it. Should we stay away from this functionality?
>
There are plans to eventually make this API, but will not be API in WTP =
1.0.
There is some question if this should/could move to be part of the
base Eclipse platform for 3.2. My guess at the moment is that if it does=
not,
it will become API in WTP 1.5. (That decision will probably come in Janu=
ary or February
of next year).
I would say its "safe" to use, in the sense it will not "go away" or cha=
nge fundamentally,
but, if you use it, you will need to allocate the time and plans to "kee=
p in synch" as it gets
changed from one release to the next. Despite our best efforts to "be co=
mpatible", it
will undoubtedly require some adjustment from anyone who uses it, and al=
l that implies
about "re-releases", etc.
|
|
|
| Re: Tab Property Pages are internal?? [message #147762 is a reply to message #147640] |
Fri, 18 November 2005 16:53 |
| Eclipse User |
|
|
|
Originally posted by: bob.donovan.ugs.com
David,
Thanks for responding.
Bob
"David Williams" <david_williams@us.ibm.com> wrote in message
news:op.s0exyzcxac05ss@dmw2t23.raleigh.ibm.com...
On Thu, 17 Nov 2005 17:49:39 -0500, Bob Donovan <bob.donovan@ugs.com> wrote:
> Typically this means we should not use this class and therfore even the
> extension point.
>* Can someone tell me if it is safe to use this extension point? * Are
>there plans to make it public?
> * The fact that this is internal may mean that we should not be extending
> it. Should we stay away from this functionality?
>
There are plans to eventually make this API, but will not be API in WTP 1.0.
There is some question if this should/could move to be part of the
base Eclipse platform for 3.2. My guess at the moment is that if it does
not,
it will become API in WTP 1.5. (That decision will probably come in January
or February
of next year).
I would say its "safe" to use, in the sense it will not "go away" or change
fundamentally,
but, if you use it, you will need to allocate the time and plans to "keep in
synch" as it gets
changed from one release to the next. Despite our best efforts to "be
compatible", it
will undoubtedly require some adjustment from anyone who uses it, and all
that implies
about "re-releases", etc.
|
|
|
Powered by
FUDForum. Page generated in 0.03706 seconds
] 
Search
Help
Register
Login
Home
