I save the reference as l_parent and then use it in the event
handlers to invoke methods defined in the main application. The idea
is that I might want to use it connect to MySQL, sign in to VistA, or
something else. Anyway, the dialog isn't supposed to know what you're
doing when you log in. The good thing about this design is that it's
flexible. The bad thing is that it means that lot of application
logic gets stuck in subclass of Frame. If you want to sound jaded,
you can say that it is poor cohesion, if you don't, it violates the
principle "Do one thing, and do it well".
===
Gregory Woodhouse
[EMAIL PROTECTED]
"Education is a progressive discovery
of our own ignorance."
--Will Durant
On Jul 12, 2005, at 5:49 AM, Kevin Toppenberg wrote:
I've done very little with java, so let me feel my way
here.
I assume that function public LoginDialog is the
constructor for class LoginDialog. I see Frame passed
as a parameter to the constructor, but I don't see
that you use it. What is it doing?
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
