[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] "opening up" PropertySheetViewer
|
John
The API freeze was some time ago so there will not be any more feature
work in the 3.2 timeframe. Looking at both bugs I have noticed that they
have no votes - if enough members of the community vote on these we could
look into them for 3.3.
Adding votes to bugs really helps us determine the issues that are
important to the most people.
Tod and Boris (Platform UI team)
"John Ruud" <jruud@xxxxxxxxxxxx>
Sent by: platform-ui-dev-bounces@xxxxxxxxxxx
05/18/2006 12:24 PM
Please respond to
"Eclipse Platform UI component developers list."
To
<platform-ui-dev@xxxxxxxxxxx>
cc
Subject
[platform-ui-dev] "opening up" PropertySheetViewer
There are currently a few feature requests (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=91749,
https://bugs.eclipse.org/bugs/show_bug.cgi?id=4584) for allowing users to
customize how items are rendered in the PropertySheetViewer. It is
probably way too late to get anything included in time for the 3.2
release, but I was hoping it would be possible to open up the viewer for
extensions ever so slightly, until a more "formal" extension mechanism may
be agreed upon.
The quick work-around would be for the PropertySheetViewer class to change
from 'private' to 'public', and the updateEntry() and updatePlus() methods
from 'private' to 'protected'. This would allow us to subclass just the
viewer, instead of having to clone & maintain our own version of the
complete org.eclipse.ui.views plugin (due to the viewer accessing other
private org.eclipse.ui.views classes etc.). Is there a way to "fast-track"
this change request, so that it may make it in time for 3.2?
Thanks, John_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev
