[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: SWT Bean Persistence [Was Re: [platform-swt-dev] SWT in borlands jbuilder]
|
Any GUI builder will inevitably treat the widgets, whether they be Swing or SWT, as more than just beans. You can't build a good GUI builder by just manipulating JavaBeans. For example, a GUI builder would have to know that a JTabPane only shows one of its children at a time, and if the user want to visually drop widgets on the other tabs, there has to be a design-time way to flip pages. Split panes have to be treated specially, and so do *lots* of other things, like layout managers, constraints, menus.
So, desigining a builder that has to understand constructor-time attributes, or publicly-accessible fields, or public API that is really internal are just some of the small steps in supporting a useful SWT GUI builder.
Bean support is not all you need to create an AWT/Swing GUI builder, so why should SWT conform to a spec that doesn't give you any real benefit? (That's a rhetorical question, just my 2 cents)
Randy Hudson
