| Generic PropertyEditors for type Object and Interfaces [message #24103] |
Tue, 09 March 2004 11:41  |
Eclipse User |
|
|
|
Originally posted by: dcarlucci.sigma-iface.com
We have developed a huge amount of panels with VisualAge-VCE. We are
evaluating eclipse and VE as future IDE and visual editor and it seems to be
the right choice for us.
We are using Eclipse 2.1.2 and VE 0.5.0.
VCE of VisualAge for java has two PropertyEditors that we miss in VE
1. a generic PropertyEditor (CellEditor) for type Object that allows to
enter any code strip as String (new MyClass(), "anyString", etc.)
2. a PropertyEditor (Dialog) for interfaces that lists all implementors in a
ComboBox or alternatively allows to enter a code string (see attached
picture)
Are this two PropertyEdiotors planned for future releases (1.0 or earlier).
If not, how should we solve this problem (create custom editors and
configure the
OVERRIDE-Files???) ?
Any help would be great!
thanks in advance,
Donato Carlucci
|
|
|
|
|
| Re: Generic PropertyEditors for type Object and Interfaces [message #24516 is a reply to message #24471] |
Wed, 10 March 2004 10:07  |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Those are nice ideas. But they aren't implemented. Other than you
writing an Eclipse VE property editor to do this there is no current
workaround. Sorry.
You can open a bugzilla enhancement request so that the idea won't get lost.
--
Thanks, Rich Kulp
|
|
|
| Re: Generic PropertyEditors for type Object and Interfaces [message #583971 is a reply to message #24103] |
Tue, 09 March 2004 13:41 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Those things are now actually easier to enter straight in the code. Just
click on the part that you want to add the property for, and then go
to the source view. The code has been driven to where you can add
property settings and just add it. That way you have full code assist
support. This works for the Interface just as well. Full code assist is
available there.
--
Thanks, Rich Kulp
|
|
|
| Re: Generic PropertyEditors for type Object and Interfaces [message #584128 is a reply to message #24123] |
Wed, 10 March 2004 09:20 |
| Eclipse User |
|
|
|
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:c2l2tl$bls$2@eclipse.org...
> Those things are now actually easier to enter straight in the code. Just
> click on the part that you want to add the property for, and then go
> to the source view. The code has been driven to where you can add
> property settings and just add it. That way you have full code assist
> support. This works for the Interface just as well. Full code assist is
> available there.
>
>
> --
> Thanks, Rich Kulp
>
>
Thanks for your prompt answer.
Yes of course... and I like the facility that you are driven to the place
where to add the code and that you have full code assist.
On the other hand we loose some informations defined in the BeanInfo.
> 1. a generic PropertyEditor (CellEditor) for type Object
> that allows to enter any code strip as String (new MyClass(),
> "anyString", etc.)
Supposed we have a property on a Subclass of JRadioButton named
"deselectValue" and that this property is not yet set in the code because it
is configured with default value. If I want to set a new value I have to
know which setter to use. With code assist I get all public methods of a
type (Ok, in most cases the setter is given by name convention (propName ->
#setPropName)). But if there are more than one setter with different
signatures you may use the wrong one. But the BeanInfo knows very well which
setter to use.
> 2. a PropertyEditor (Dialog) for interfaces that lists all
> implementors in a ComboBox or alternatively allows to enter
> a code string (see attached picture)
In this case we have the same "problem" as mentioned before. In additon to
this we don't have the ability to get all implementors of an Interface with
code assist (or am I wrong?). Further, the PropertyEditor dialog of VCE of
VAJ was able to list all propertis of the current selected implementor
evaluating the BeanInfo of the selected type (each implementor has a
different number of configurable properties defined in the concerning
BeanInfo). If one of this "nested" properties was an Interface itself you
got another PropertyEditor dialog (same type of PropertyEditor) to configure
this... and so on (see attached pictures).
We have developed a framework to easier devolop company specific
applications. This framework contains a lot of subclassed beans. With VCE of
VAJ it was easy for framework users to use and configure this beans because
they didn't have to know the beans in detail and they where driven through
the configuration by the PropertyEditors (especially the Interface
PropertyEditor). That's why we need a solution for those problems to provide
the same comfort to our framework users.
Any hint would be appreciated.
Best regards,
Donato Carlucci
|
|
|
| Re: Generic PropertyEditors for type Object and Interfaces [message #584142 is a reply to message #24471] |
Wed, 10 March 2004 10:07 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Those are nice ideas. But they aren't implemented. Other than you
writing an Eclipse VE property editor to do this there is no current
workaround. Sorry.
You can open a bugzilla enhancement request so that the idea won't get lost.
--
Thanks, Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.04434 seconds
Home