> > And make things explicit. Make the BufferStrategy > in Swing explicit. Basically, make Swing be an > actual disjoint layer above AWT/Java2D, utilizing > ONLY the public, userfacing APIs of AWT/Java2D to > work (I don't really > now how far from that it is at this point - but I > still feel there are some magic involved..) > > I doubt this will happen. Whether or not swing > uses buffer strategy > underneath is an implementation detail you > shouldn't care about. > There's tons of technical reasons why this can be > done anyway.
I guess you meant "can't"? Could you share one or two of these technical reasons? See, given only AWT and Java2D, I can't seem to grok why it wouldn't be possible to implement a complete "pixeling" widget toolkit aka Swing that does not utilize the underlying windowing system except for lower level primitives like window/canvas/frame and painting? Why would one _need_ tricks beyond the public-facing APIs from AWT and Java2D to make Swing? Wouldn't such a separation make for easier to understand APIs, where Swing was just an application using the sole graphical interface to the host (AWT/Java2D) that Java provides? I do understand that the latter are philosophical questions, at least at this point. But any light shed would be very nice. Thanks a lot, Endre. [Message sent by forum member 'stolsvik' (stolsvik)] http://forums.java.net/jive/thread.jspa?messageID=298165 =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA2D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
