Is this really a dilemma? Does the book makes us embrace hardcode in desfavor of auto generated code from IDEs? In times of costs reducing, is it still worth the time consuming han(r)d code instead of instant produced gui with IDEs? Can the book make me choose the hardway of doing it, showing me the really advantages?
My non-book related 2-cents worth... If there was 1 IDE that everyone used to code GUI's then I would be all for it. As open as the Java Community is and as many choices as there are this makes things difficult for GUI builders in an IDE. The reason for this is there is no common standardized structure for spitting out the source code. Also, most GUI builders that I know of (Netbeans in particular) write some pretty nasty code for the GUI that I wouldn't dream of doing. So future maintence of an application can become a nightmare because you are trying to dicipher what an IDE spit out. Granted this is the same case if a developer hand codes the GUI for someone else to maintain, but chances are it will be structured better. Anyway, with all that being said, even if there was a standardized structure for IDE generated Swing source code, I would still do it all by hand.
wow, that's interesting... this is probably a better reference by far. mine is more or less my interpretation of it as it was passed along to me... [which i deleted, but i realize i removed the pertinent comment, which is that it was irrelevant to this thread and should have been in a signature] apologies for detracting.. - maggie [ April 27, 2004: Message edited by: maggie woo ]
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Swing: handcode versus IDE generated code