Models, Controllers and Views in detail

The MVC-O framework essentially supplies three base classes which implement respectively a View, a Model and a Controller. Developers have to derive custom classes from the base classes set, adding the implementation which depends on the application semantics.

Model base class

Supplies servicing for:

• Fully automatic Observable Properties
• Automatic broadcast notification when observable properties change.
• Transparent notifications to observers running in the PyGTK loop, even when sent by models running from other threads.

Controller base class

Supplies servicing for:

• Automatic registration as observers of the associated Model.
• Easy access to the associated Model and View for any derived class.
• Instantiation of adapters.

View base class

Supplies servicing for:

• Automatic widgets tree registration. Input can be a set of root widgets stored inside a Glade File, or a completely customized widgets hierarchies.
• Automatic registration inside the associated Controller.
• Automatic signals connection to methods supplied by the associated Controller.
• Widget retrieval inside the set of hierarchy. Widget can be accessed by using the name they have been defined from within Glade, at design time, or that have been specified when creating widgets by hand.
• Support for custom widgets declared in Glade files.