In Swing GUI development, do you code by yourself or use power tools?

[www]

Hi,

In writing Swing GUI programs, I have seen people write the code line by
line. I also found that there are a number of Swing GUI development
tools available (some are free, some are not). Using those tools, you
just need to drag a button, drop to the client platform, etc. And code
will be generated for you automatically.

I am curious what is advantage/disadvantage for the two choices.

Actually, my project leader use the first method - code line by line.
The GUI he developed is not trivial. Now we need to make some
modification to the GUI. I have to code line by line, correct?

How about JavaBeans? JavaBeans is almost never talked in most Java
Books. But occasionally, I saw it is used.

 

[Lew]

How about JavaBeans? JavaBeans is almost never talked in most Java
Books. But occasionally, I saw it is used.

JavaBeans as such are not such the buzzword any more. For most people, use of
JavaBeans amounts to no more than following the conventions / mandates for
getX() and setX() methods (accessors and mutators). The JB spec has much more
- listeners and notifications, most notably, and property sheets.

Actually, JavaBeans are quite powerful. Researching this post I ran across an
article at Sun
<http://java.sun.com/j2se/1.4.2/docs/guide/beans/changes14.html>
that tipped me off to some classes I can use in current projects.

Get the whole schmeer at
<http://java.sun.com/j2se/1.4.2/docs/guide/beans/>

Y'know, it took less than five minutes for me to turn up these links. I just
opened <http://java.sun.com/> and used their search box.

-- Lew