| [e4-dev] Model tweaking round 3 - The proposed subpackage structure |
Hi,
I'm just preparing for tomorrows e4-call and thought it might make sense
to describe the idea behind this new structure before the call (to some
extend also because for none native speakers like me it's easier to
write things up :-).
Attached to this mail you'll find a complete Package-Diagram of our
newly structured Domain-Model.
The structure is like this:
+ application
+ commands
+ ui
+ menu
+ base
+ extended
+ descriptors
+ base
The main driver for this structure is that in my idea our domain-model
holds 2 different things:
a) An UI-Layer: which acts like a browser DOM and makes up the UI of
our workbench (=> Elements are interpreted by a renderer) it
reflects the current UI state
b) Application-Layer: which holds the commands with the application
logic, contributed descriptors. It's fairly hidden from the
Application user.
Now that I outlined the main driving reasons for the model-structure I
hope this also explains why HandledItem & HandledToolItem &
HandledMenuItem are part of the UI-Layer (the get renderered).
Things I'm not sure of:
* Anybody a better name than menu because it holds toolbar and menu
stuff
* Anybody not in agreement that HandledItem/HandledToolItem
/HandledMenuItem are part of the UI layer
* Any missing subpackage you want to see
Tom
--
B e s t S o l u t i o n . a t EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl geschaeftsfuehrer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5/1 A-6020 innsbruck phone ++43 512 935834
Attachment:
UIElements.png
Description: PNG image
