> I'm going to out on a limb and assume you're using Swing here. =A0To keep=
 the
> GUI painting properly and new events being processed you have to make sur=
e
> the EDT (event dispatch thread) does not block. =A0So in your event handl=
er
> you need to spin off a new thread and return as fast as possible to preve=
nt
> "laggyness" in the UI. =A0This does mean you need some asynchronous way o=
f
> getting your response, a queue is probably your best bet here (plus it's
> thread safe). =A0InMonkeybars, we used a library named Foxtrot (Java lib)
> that processed GUI redraw events (but not new actions) while an action wa=
s
> being performed. =A0For short-lived processes this worked great and preve=
nted
> the mess of having to get data back from an asynchronous thread.
>
> David Koontz
>

Yeah I started using MonkeyBars. I find it a very interesting project,
but complicated to learn (may also since the tutorial videos don't
seem to work ;) I'm gonna stick to it though because it combines so
much great stuff (Ruby style, Swing power, "neo"-MVC, neat folder
structure, deployment, ...)