I'm working in a domain using well known objects ... let say, water distribution.
The objects are, most of the time, always the same.
- Distribution pipes
Most of the time, the first things to do is to layout all the objects and make connections between them. For instance, layout the water distribution of a city. It seams that I can do this in an easy way with the new (beta) diagram feature, using WPF and MVVM.
It seams really nice by the way!
Let's complicate the thing a little bit.
I would like my application to be modular. I discovered prims/unity. Searching your blogs/forums, it seams feasible to use rad controls in a prism environment.
I found some ways
to use RadDocking with prism and also some examples
on how to use the ribbon with prism.
But founding no "Here is the way to do" solution, I known that it won't be as easy as the diagram part, but that's OK for me.
Here is the funny part.
Let's say there is an existing diagram for a city.
All the layout is done and I can have basic information when I'm selecting an element (the kind, a part number, the color, the placement, the links, etc.)
But after that, I would like to have a set of .dll files to add or remove from the application installation folder that will adapt the application so that it can be used by different people. But keep in mind that the diagram is always the same.
As an example, take the maintenance team and inventory team as 2 separate kinds of users.
By clicking on a water pump, I would like to have a new/expanded property view (and even ribbon tab, commands) that are designed by kind of user:
- Maintenance : when was the last maintenance and who did it, when is the next one and who will do it, etc.
- inventory team : do we have spare parts and how many. Where are the parts buy, what is the cost, etc.
I could also have new diagram element that can be added to the existing diagram.
The idea is that my data repository contains all the information for my domain object, but I want to be able to have a modular application displaying only the necessary part that could interest the user. In fact, it could be sold as 3 different applications if necessary.
My question is :
- It seems easy to build a diagram
- It seems feasible to build a diagram inside a modular application
=> It is possible to build a modular diagram application so that it fill the needs explained in the third part of this post?
Any advice or real experiences are welcomed.