| separating business model from view model [message #200580] |
Tue, 25 October 2005 15:45  |
Eclipse User |
|
|
|
Originally posted by: jkarlik.info.fundp.ac.be
Hello,
I would like to know what's the main advantages of separating business
information from views information? Is it only an advantage when we want
to provide more than one representation for one business model element?
It's obvious that I don't want to pollute mu business metamodel with all
graphical stuffs (colors, coordinates, row numbers, etc...) and I would
like to persist the changes of the users. So when the user highlights
some elements in the diagram and then close the diagram and then open it
again, the last selected elements must be yet highlighted. So I think
that i have to keep track somewhere in my metamodel of the current
graphical state of my metamodel representation. But where? in the same
model or not? We can think of my application a little bit as the famous
XML engine "XMLspy" to view XML documents. I would like to provide the
best architecture for my metamodel.
What would be your best advice to link together the two models (business
and view)? Which one must reference to the other?
|
|
|
|
Powered by
FUDForum. Page generated in 0.05265 seconds
] 
Search
Help
Register
Login
Home
