Sean Cribbs wrote:
> Actually, after messing with my peer-toolkit hack for long enough, I'm
> inclined to agree. Mixing AWT and Swing is just too messy. Of course,
> that doesn't mean we have to forgo having PL&F in standard AWT. I think
> using the Swing UI delegates directly won't work, because one way or
> another they require a JComponent (and probably typecast to whatever
> subclass they are working with). Instead, I'm going to investigate
> making the L&F pluggable at the peer level. Since our peers will never
> make graphics calls directly through native libraries, but instead
> through some Screen or GraphicsDevice object, our system is essentially
> lightweight. I think I will botch my old code and start some new stuff,
> mimicing Swing's idea of the UIManager-JComponent connection in the
> Toolkit-Peer connection. Unfortunately, this means that the AWT L&F
> will be separate from and independent of the Swing L&F, but I see no
> reason why we can't create AWT L&F's that look like the Swing versions.
> Then, hypothetically, a user selecting a particular look and feel could
> have the two L&F's changed in tandem. Anyway, those are my ideas for
> now.
what if all your peers subclassed from JComponent? wouldnt that solve
many of the problems. you create a superclass that does the standard
configuration for JComponent (seeting isOpaque to true and the like) you
wouldnt need to change the L&F's in tandem since the peers would be
linked to the UIManager (I think)
just an idea
Cheers,
DigiGod
_________________________
[EMAIL PROTECTED]
AIM:DigiGod 86
_________________________
Quote of the Moment:
Thus spake the master Ninjei:
"To the intelligent man, one word, to the fleet horse
one whip, to the well-written program, a single
command"
_________________________
Prank of the Moment:
Using the conferencing feature of your office phone, dial
one Induhvidual, then while it's ringing dial another and
conference them together. Put your own phone on mute
and listen to see how long they'll make small talk before
figuring out that neither one placed the call.
O-
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
