|Re: [e4-dev] Declarative UI in E4|
Kevin,In wazaabi 2.0, I choose to use 2 metamodels: one is abstract and holds the behavior which is not SWT specific. The second one is concrete and tries (with respect to the abstract one) to be as close as possible to SWT. This has been done for allowing other concrete models like Swing (which is not one of the first target of E4, I know). The runtime engine is split up into 2 parts respecting the separation of metamodels. The mechanism is based on controllers which manage views (1 model <->1 controller <->1 view) and the view contains usually a widget. The view creation is not dependant of the parent, even if the underlying SWT widget is.
It allows the reparent of any view and/or provides skinning capabilities.This separation allows also stylesheet mechanism (not implemented yet). (A button could be systematically embedded in a container)
IMO, having a 1:1 mapping means we just reproduce the implicit model of the APIn then we accept as a model langages constraints. For instance, for the checkbox button, is the selection (check) an event or a property ? In wazaabi it acts as a property (and of course, EMF allows us to add Adapter on it). My current work is focused on databinding model & engine. After this (important step), I will try to build E4 demo using wazaabi.
Regards, Olivier Kevin McGuire a écrit :
Back to the top