Using visual UI designers

Previous | Next

By bloid
via pushing-pixels.org
Published: Dec 07 2007 / 18:26

If you ever needed an argument against using a visual UI designer that enforces any logic on the code it creates, here it is:

Vote up

Vote down

15
7
1542
705

Save Send Tags: gui, java, tools

Upcoming Links

See all the newest links

Comments

Add your comment

zaph0d replied ago:

0 votes

down vote, only because it tries to sell you "the one and only solution", which of course, isn't.

Eraserman replied ago:

0 votes

The entry is meant to be an attack on the NetBeans GUI Builder. It says that since JBuilder dropped support for their GUI builder the same thing might happen with NetBeans in the future.

There is a big difference between NetBeans and JBuilder. JBuilder was (and still is) a proprietary application, if Borland decides to drop support for the GUI Builder there is nothing anyone can do. NetBeans, on the other hand, is open source, if Sun tomorrow decides not to support the GUI builder, there is nothing stopping anyone from taking the code and supporting it.

Although nowadays I don't write client code, at one point I was against GUI builder because they locked you into proprietary solutions. Today, if I had to write a Swing application I would have no trouble using NetBean's GUI builder, since it isn't proprietary and I know it can be supported indefinitely in the future.