Right. And interestingly, JSR-295 (beans binding) and JSR-296 (app framework) was all about living without an explicit model. Swing MVC is extremely flexible but also complex and verbose making it darn hard to master (who updates who, and when, in which thread, how to avoid cycles etc.)
/Casper On Nov 2, 3:08 am, Christian Catchpole <[email protected]> wrote: > Yes, Swing was part of the write-once run anywhere ideology, which > works fine for the rest of Java, but is somewhat in denial when it > comes to the GUI. When people didn't want non-native looking windows > they had to back fill it with emulation.. which in my opinion is > totally freakin' stupid. You can argue that SWT doesn't have a proper > model, but that would be picking on SWT, not the broader argument of > emulated vs native. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
