[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ve-dev] VE 1.5 development plan
|
Java is not a good solution to store UI structure:
1. Difficult to decode and encode
Difficult but not impossible as can be seen with WindowBuilder. We
can decode or encode in virtually any Java-based style and can
readily read and write code written by any of the other Java GUI
builders out there (including the VE, NetBeans, JBuilder, etc.). We
can also do it natively in any of those formats (and many others)
without requiring the user to re-write, reformat or otherwise
restructure their code.
2. Static aspect and business logic are mixed up, it is always a mass
That hardly needs to be true. If you can split your app into GUI code
(XML) and business logic (Java), you can just as easily do both in
Java as well, and avoid the impedance mismatch between XML and Java
on the GUI side.
3. Very limited to support advanced features such as data binding,
reusable component, etc
I very much disagree here. Java is by far the best approach for
dealing with custom and reusable components that themselves have also
been created in Java because you can talk their native language and
not try to shoehorn everything into an entirely different language
like XML. WindowBuilder, for example, has excellent and very
comprehensive support for the Eclipse Data Binding API (as well as
Swing JSR 295). We also support a variety of component reuse models
including the creation and consumption of custom Composite and custom
widget factories.
Regards,
-Eric Clayberg
Sr. Vice President of Product Development
Instantiations, Inc.
mailto:clayberg@xxxxxxxxxxxxxxxxxx
http://www.instantiations.com
Eclipse Productivity. Enterprise Quality.
Author: "Eclipse: Building Commercial Quality Plug-ins"
http://www.awprofessional.com/title/032142672X
Author: "Eclipse Plug-ins"
http://www.awprofessional.com/title/0321553462