More on the client side, I common complaint I read is that Swing lacks a 'Pet
Store' application,
like the J2EE example, that shows new developers the best practices for putting
a non-trivial
application together. How do you architect your system? There are many
flavors but they all (at
least the ones I've heard of) implement some sort of MVC or MVC/D. The devil,
of course, is in
the details. How do you try to implement code reuse so that you don't
copy/paste all that JTable
code around? How do you bind widgets to data? How do you handle events so as
to not violate MVC?
What do you do about that 2000 line uber-controller or uber-model class?
Many questions and many different answers depending on your style and exact
problem.
Ray
Discover Yahoo!
Get on-the-go sports scores, stock quotes, news and more. Check it out!
http://discover.yahoo.com/mobile.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
