Sean Cribbs wrote:
> I agree that a direct ui connection would be much faster, however, I
> chose to create them the first way for several reasons:
> 1) We don't have to implement the peer-level functionality of each
> component, we only have to make wrappers to the already-implemented
> functionality of the Swing-level component.
> 2) If the user decides to change the look and feel, the peers would have
> to be notified in some way so that they don't maintain links to the old
> UI delegates.
That shouldnt be to hard, we'd just need to copy how they do in Swing...
> 3) Wrapping Swing components into the peers is easier than using the
> delegates (i.e. I'm lazy). Besides, when a UI is asked to draw, it
> requires a JComponent to be passed. Why not just leave all of the
> complications to Swing?
well thats fine for now, but Im saying eventually we should redo it the
better way and we might as well figure out how to do it now.
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
