> I'm going to out on a limb and assume you're using Swing here.  ¨Βλεεπθε
> GUI painting properly and new events being processed you have to make sure
> the EDT (event dispatch thread) does not block.  ¨Βιξ ωους εφεξθαξδμε> you need to spin off a new thread and return as fast as possible to prevent
> "laggyness" in the UI.  ¨Βθιδοεσ νεαξ ωοξεεδ σονε ασωξγθςοξουσ χαοζ
> getting your response, a queue is probably your best bet here (plus it's
> thread safe).  ¨ΒξΝοξλεωβαςσ¬ χε υσεδ μιβςαςξανεΖοψτςο¨Καφμιβ©
> that processed GUI redraw events (but not new actions) while an action was
> being performed.  ¨Βος σθοςτ­μιφεπςογεσσετθισ χοςλεδ ηςεααξπςεφεξτε> 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, ...)