Re: Understanding Object Usage

James Perkins skrev:

Ah.. ...that makes sense for the ConnectionBean. I have done refactoring
before, I'm just always paranoid that it misses something. I guess it's time
to start trusting it. ;-)

Take small steps and evaluate carefully. Do not just take my word for it. Generally I have found that the refactorings in Eclipse are quite reliable, and extremely useful.

See a complex expression? Mark a sub-expression and extract it to a local variable and give it a sensible name! See a long method which is hard to comprehent. Mark blocks and extract them to methods and give them sensible names. See a badly chosen identifier, rename it :)

Refactoring allow you to put the knowledge you would normally put in a comment, in the code!

I agree with the JSP thing. I some times put Java code in the JSP and I hate
doing every time. I just wrote my first simple JSF page and I can see where
this would be very powerful. And yes, my problem was putting it into
production. Luckly it's a small shop and that's basically how I learned all
my programming is by writing various programs there.

Great. Gives you the joy of maintaining your own stuff for years to come :) Always a learning experience.

Probably a question for a different post, but hand code vs. WYSIWYG for JSF
and Swing UI's? I have done both, but I see conflicting information all the
time about this.

I use hand coding in MyEclipse for JSF, but it has a visual representation concurrently where you can see what you do, and how it looks. It also allows you to navigate quickly to a given component just by clicking on it, and has completion on attribute names etc. That works well enough for me.

For Swing the Matisse editor in Netbeans is incredible! The MyEclipse folks have portet a large portion of it to Eclipse. The Visual Editor is also quite nice as you can both do visual stuff and hand edit.

Regardless of what you choose, chose one that allows you to keep working with the GUI-version after you hand-edit stuff.


/Thorbjørn