Re: Coding Challenge
- From: Chris Smith <cdsmith@xxxxxxx>
- Date: Fri, 30 Sep 2005 09:42:31 -0600
Roedy Green <my_email_is_posted_on_my_website@xxxxxxxxxxxxxx> wrote:
> Newbies often bring problems to the table that suggest they have done
> something to tie up the swing thread either by giving it some lengthy
> task in an event handler or even going to sleep.
>
> 1. What I would like is something a newbie could tack onto pretty
> well any GUI app that can detect that, and perhaps even diagnose where
> it is happening.
>
> 2. this one is more difficult. People often poke Swing components
> from the non Swing thread. How could you create a wrapper around all
> the Swing components to detect that abuse in a way even a newbie
> could use it? Perhaps there is a way using the JXTA debug interface
> to pull it off in Java.
This is one of the few places where AOP sounds interesting. AOP could
be used to solve SOME of #1 (intercept uses of certain blocking APIs
from the EDT) and pretty much all of #2 (intercept calls to Swing
components outside of the EDT) at runtime. Of course, building the
rules for #2 could be tedious, as you'd need to go through all of Swing
and determine the rules for when it is/isn't safe to access something
through a non-EDT thread.
--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.
Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation
.
- Follow-Ups:
- Re: Coding Challenge
- From: Roedy Green
- Re: Coding Challenge
- References:
- Coding Challenge
- From: Roedy Green
- Coding Challenge
- Prev by Date: Re: editor how to
- Next by Date: Re: editor how to
- Previous by thread: Re: Coding Challenge
- Next by thread: Re: Coding Challenge
- Index(es):
Relevant Pages
|
|