[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ve-dev] VE 1.5 development plan
|
Making an extra file to store the gui in (like netbeans does) is bad
if that file goes out of sync or is lost that .java file basiclly
becomes useless.
I hope what they mean is to use XML to represent the GUI as a
complete alternative to Java and not have two files (XML and Java)
representing the same thing. The former can work, but the latter is
downright dangerous as is the case with NetBeans. One of the basic
principles of data normalizations is that it is always a bad idea to
have two data structures (or two files) represent the exact same
thing. That is a recipe for disaster as they will always get out of
sync eventually or the primary file (the XML .form file in the case
of NetBeans) will always get lost.
I am not against the idea of delarative ui, im only against what
netbeans gui desginer does (That extra .form file that sometimes
goes out of sync or is lost and leaves you stuck)
The NetBeans GUI builder is quite primitive under the covers (with a
very sexy exterior) as it can't even parse its own generated Java
code. That makes its reliance on .form files particularly dangerous.
We have rescued many dead-in-the-water NetBeans projects with
WindowBuilder's ability to both read and write the NetBeans GUI style.
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
