From: "Danny van Bruggen" <danny / froukepc.dhs.org>
[...]
> > In the end, I think that the best solution is to design GUI API for Ruby, and 
> > then require toolkit bindings to conform to that API.
> 
> Yes, I wonder if I can find the border between... WM and TK? in Swing.
> 
> > the user to plug in a variety of subsystems.  The biggest problem is,
> > of course, the AWT LCD issue, but I believe that some of Ruby's
> > features would help to alleviate these problems.
> 
> LCD issue? What's that? Google mentioned Lowest Common Denominator
> programming, is it the issue that AWT can only do what all its supported
> platforms do and nothing specific? That should be solved in Swing, I
> thought?

Not sure if this is relevant or useful, but the discussion here
reminded me of a wiki page:
http://www.c2.com/cgi/wiki?TheStoryOfAwt
(about the route by which AWT ended up utilizing native peering...)


Bill