Hi Svenn, Originally posted in cdnusers.org by Britta
I don't think the library manager is the problem for DM, it just makes an underlying problem more visible.
I have worked on projects, where I counted in total 126 different 'layout' view names. Some cells had
up to 10 different layout view names like layout_new, layout_save, layout_good, layout_2 etc.
This is working style, personal preference, being afraid of loosing things...
Data management does require a complete new way of thinking.
If I am following the DM paradigm, then I check-in my work at stages, where it means something to me e.g first part of
a functionality is implemented.
I put useful comments in the log message, that hopefully still mean something to me in 6 months from now and hopefully
somebody else does understand them too.
I can go back to any earlier version that I checked in. This is nothing else then having layout_new or layout_save,
just that they are named differently now.
How many of those versions you see, depends on the work model you use. If you use a shared work model where many
people work in the same work area, then yes, that can be plenty. If you work in a private work model, where the configuration only belongs to you, then you are the owner of what you see.
A good way to deal with exploding views is to come up with naming conventions. You can enforce them with access controls
if you want.You can not prevent them from being created, but you can prevent the users from checking them into your data base.
I personally would not like to see something to be greyed out. You limit users what they can use or do and if somebody
really wants to use schematic_1_2, why not? BTW, Only the DM tool could determine if something is managed or not.
The library manager is coming from Cadence. Yes, it can be customized or completely re-written. That would have to be done
from the DM vendor though.