I've been thinking about how to rewrite parts of the signal/slot mechanism in scala, primarily to get compile time compatibility checking and not needing class instances for slots. Also, you can get some really nice syntax sugar for making any property a signal, auto-emitting, and property bindings.
I've already implemented something similar to this for use in domain logic. A straight forward signal/slot system itself is simple enough, but clearly the one in qtjambi does a lot more than this. So I need some help from someone with some insight to the current signal extension on how to attack this problem. First of all, what does the internal signal emitter actually do, and what concerns should be made (native signals and such) if you were to reimplement it? Or maybe its possible (and easier) to somehow do a simple wrapper around the existing java implementation?
_______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-jambi-interest
