> Mouse events are delivered to the application by the OS in an event queue.
> The "application" in this case is the JDK, and the event queue is exposed
> through the AWT. AWT delivers to heavyweight components, and from there
> Swing receives and despatches to lightweight components.
Aha! Thanks, Steve.
Just started digging into EventQueue, Runtime, Shutdown etc. :-)
> Agree with you on the hierarchical models, and in fact scope models are
> already hierarchical in the sense that they can contain other models (as
> properties). There is support for some of the subtleties that arise from
> this in the BasicController's handling of MODEL_CHANGED Controls. I can
> explain that handling some more if you like?
Thank you but I'm currently into other parts of our framework. I will
definitely ask you again when needing help!
The idea behind our framework is slightly different. I've taken the
human body as example for modelling and it works perfectly.
The system/application is a human being having organs (View = Eye,
Controller = Brain etc.) as components which are built up hierarchically
within the initialize methods and destroyed properly by the finalize
methods, so that a complete lifecycle of each component is assured.
In my thinking, a gui component of the view should be able to have
their own ControllerComponent (Brain/Nerve Cell), reacting to signals/
events, quite similar to the event handling of HMVC/Scope.
But I plan to avoid sending signals which are created somewhere and
not properly destroyed because they don't belong to a specific object.
(Garbage Collecting is not enough for me, I want to destroy all objects
properly by calling their lifecycle methods in the right order, at a
defined time.)
That means, that a gui component (eye cell) has to call some method on
its associated controller component (nerve cell) and is only allowed to
hand over references to already existing objects, not creating new
signals/events which would be sent into Nirvana.
Does this all make some sense to you?
Christian
|
