Topics and plan for the Lille dev sessions:

Metamodel

View instancing order (*)

When instancing, sometimes some view nodes need to wait until other nodes are instantiated.. how to do this?

Review Hierachical Views (*)

There is a new Hierarview by dukez. We need to:

review this system throughly DONE
create some unit tests DONE (more can be done)
fix problems:
- merging/splitting of model/view relations
- sharing of views just by class
- view notification when parents added/removed

Child ordering <-> deferred loading (+)

Metamodel needs explicit ordering of nodes, this can be done on children or through some other mechanism. The main problem is at the moment there is also a mechanism for deferred loading, for situations where all the iniformation to load a node is not known when the application starts. In this situations, the ordering can be modified, as models are readed to the graph later on.

We're probably keeping this.

Ontology -> Namespace

There is some debate about ontology being used in the right way on metamodel.metamodel. Main idea is to change the name to Namespace, and use this to finish implementation of namespaces for mm.

DONE: rev 310 and 311

Modification Tracing

Dukez proposes a generic subsystem for mm to log modifications, and possibly undo them, possibly supporting transactions.

It should refactor out some code from the undo manager in caf.

Constraint System / Inference

Dukez proposes a constraint (sub)system together with an inference system to enforce constraints. This could provide more expressivity and power to mm.

Hard modelling problems

Some hard modelling problems have been found, when modelling the following domains:

Animation system in mm
Material system from caf:mmcommons:model3d
FSM model from caf.mmcommons:entitymodel

CAF

Streamline initialization

Services should probably be loaded from a folder instead of from top level of a file, this will allow to reference this folder easily, and also to make created services be saved with the application root by default (desired behaviour).

Caedes thinks a lot of crap has to be removed from the initial service management.

Reviewed and new order proposed: New Initialization Proposal

Code Review

Entering points for new devs
General code review

Replace with true component system

There is ongoing work to select a component system for caf as detailed elsewhere. At the moment the main candidate is Fractal, but at least caedes needs to understand it properly before using it :-) .

UI Work

Standard Widgets

The following standard widgets have been proposed (and accepted):

Action Button
Menu
Toolbar

Remove Top level delegates (+)

At the moment the delegate system from kiwi pollutes the interface subsystem unnecessarily. We have decided to make ui plugins become standard gtk widgets.