No argument here... Swing is a pain in the arse under the best of
conditions. I'm not sure just having resource files would make it not
so, but it couldn't hurt. Frankly, for me, if I'm doing a fat client
app, and assuming there is no cross-platform concerns, I'm loading up
Visual Basic and not thinking twice about it ("classic" VB I'm talking).
If it has to be cross-platform, and it can't be a webapp of course,
then Swing probably is the best alternative, as annoying as it is.
Frank
Michael Jouravlev wrote:
On 8/10/05, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
I remember having to deal with some Swing code that was created by a
junior programmer using some IDE (I forget which frankly, it's not on the
market any more - I want to say it was IBM's old one before WSAD, but I
might be wrong). The code was such an immense tangle of crap it still
makes me shudder to think of it all these years later.
The original problem is that Swing does not have resource files.
Apparently, Swing designers thought that Swing apps would have been
fluid and resizable, and it would have been hard to stick all fluidity
into a simple resource file. And now you have it. Swing code is crap
even when it is well-formatted, with these unwieldy listeners and a
forest of interfaces. There are nicer ways to create event listener
than to implement an interface with bunch of methods in it.
And now we are switching to "why programming to interfaces" thread.
Swing is a clear example why programming to interfaces is sometimes
such a pain in the butt.
Michael.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
