No slots and signals are close, but too low level. It's really closer to Swing's Event Listeners in that multiple listeners can listen to any event. I think Flex, really Flash, just did a better job at making creating your own events much easier. You don't have to repeat yourself over and over like you did in Swing. And routing events happens for you.
Charlie On Sep 22, 7:54 am, Casper Bang <[email protected]> wrote: > > Firstly, I think we still do not understand exactly what Joe means by > > a component module. Even now, 6 months after Crested Butte. > > What's not to grok? Embrace divide and conquer and realize that a > class is too fine grained. How we need higher abstractions where it's > easy to make a "kit" that fits together out of any particular context. > > > Flex sounds very much like, KDE originally architectures, what was it? > > SLOT and Connections or something. It was like a message bus inside a > > Graphics User Interface toolkit. > > Signals and Slots, the essence of Qt. Toolkit also available for Java > through > Jambi:http://www.javaworld.com/javaworld/jw-08-2007/jw-08-qtjambi.html?page=2 > > > I think what we need in the language is group binding. See above and I > > claim not to be a language designer. > > Known as multi-casting, no? > > /Casper --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
