| Clarifications on using BeanInfo customizers? [message #607365] |
Sun, 08 May 2005 15:57 |
Eclipse User |
|
|
|
Just starting to import a number of custom beans.
Couple of questions:
1) first off, since the SwingBeanInfo class has disappeared from dt.jar
in Java 5.0, is there a recommended alternative to SwingBeanInfo - a
preferred BeanInfo support class?
2) if my BeanInfo contains custom property editors, seems that VE does
not introspect the bean for properties that do not have customizers.
For example, my bean (an extension of JLabel) specifies a property
editor for get/setLineWeight and that does show up in VE's property
sheet along with the standard JLabel properties. My bean also has
standard named is/setLineEnabled methods. Since there is no need for a
lineEnabled property editor class, the lineEnabled property is not
explicitly defined in the beaninfo. While other visual editors - Jigloo
specifically - automatically find and show both properties, using a
default boolean editor for lineEnabled, the lineEnabled property does
not show up in the VE property sheet.
Is this expected behavior for VE? Must I list all custom properties if
any one has a custom editor? Or is VE looking for something in the
beaninfo to key it to also introspect the bean?
3) Is there something special I need to provide to enable use of a bean
customizer class?
In other visual editors, such as Jigloo, a double click on the bean in
the design editor will start the customizer class. In VE, double
clicking only lets me change the label text. The toolbar button
"Customize Java Bean" seems permanently disabled.
Again, is this expected behavior? How should this work?
Thanks.
|
|
|
Powered by
FUDForum. Page generated in 0.07509 seconds
Home