Level libraries in csv or xls instead of dgnlib

I think if we'd clean up the dgnlib to do exactly what they say they do and nothing more.  and then add abilities within the program where you see and understand exactly what the dgnlib impact.  then you could solve each one by one with proper utilites.  Foe example.  A very understandable level manager that shows what is in the dgnl or other drawings for you.  TOO MANY RANDOM LEVELS, DRAWINGS OR STUFF LEFT IN FILES.

This would have to be done for each dgnlib and action pair.

And create a correct path for work not 10 different ways to do something.  flexibiity is OK until it gets in the way of production.

***********************************************************************************************************************************

The problem is that dgnlibs were dropped in place with little fanfair. and if you don't have have time to explore each one and see what it does it gets too confusing.  There are absolutely too many ways to do things without direction or a possible correct path.

It should be very obvious what the dgnlib files do and what task they each are associated with.  Levels, Annotations, Floor Manager, etc.

This is a part of the front end that should be completely understood before you ever start your first project.  Just like DATASETS - I can build an entire project without DGWALLS or DGAssemblies.  You would never know from the drawings as they are the same.  I don't need a takeoff as there is no database or part list that cooresponds with Cost Works, timberline, etc..  So what path is right.

***********************************************************************************************************************************

I strongly suggest you take one day.  
Open each DGNLIB - find out what they do and either modify accordingly or create your own dgnlib for the way you work.  
Mine so far are a new  M2TextDimStyles, M2Materials, M2DetailingSymbolStyles, M2Menus, M2BB_FloorMaster.  
Now as I see a need to change or replace a dgnlib I create my own so that I dont Lose my Data.

HERE IS THE ONLY PROBLEM.  BENTLEY CAN UPDATE FEATURES IN THE ORIGINAL DGNLIB OR SOMETHING ELSE.  SO WITHOUT AN UPDATE UTILITY SOME VARIATIONS YOU MAKE CAN CAUSE PROBLEMS, JUST NOT WORK, BREAK THINGS, OR CAUSE CONFUSION WITH SUPPORT.

Add RSC files to the list as well.  I spent over an hour yesterday tracking down where a rogue Line Style was.

Its not so much that DGNLIBS are bad.  

I wouldn't mind a DGNLIB "filter", such that DGNLIB1 is ONLY responsible for Text Styles, DGNLIB2 is ONLY responsible for levels, etc.  Maybe this already exists??  Because I've had issues where spurious levels were coming from DGNLIBS with text & printstyles definitions!

I look at it as too much programming.  And what I mean here is you need to be one of us Geeks to understand it.  Need more menues and WYSIWYG controls.  A utility to control dgnlib files as well as other things too.

It is just too flexible but nothing I am suggesting taints the ability to be flexible.

The only way I knew to do this was to exploer the dgnlibs one at a time.  Clean them up and make sure they serve one purpose.  Then make sure these are my OWN dgnlib so that they don't get replaced and I can grow them.

I've just gotten to the habit of when I customize something I do it purposefully in my own seeds not in the dataset but MY Dataset.

I just thought of a good example and need.

MS go ahead and create a dgnlib for all main needs.  One DGNLIB for EACH

Create a More User Fiendly Control for DGNLIB files  (Not a pulldown list in Configure

Then a wizard specific to that dgnlib that hits all the customization needs.

You can then independently add your own.  (And don't use this as an excuse to only include a few things in the wizard.)

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

So for example:

Annotatedgnlib.

Have a dialog in MS that lists the DGNlib but not like a plan list but a smart dialog.

Tells you what you have going on.

Pick that DGNLIB and it takes you to that file

Then it open a wizard that takes you to each setting for any annotation.

A Programmer will problably tell you thi sis already there.  And basically it is but not polished.  It  needs to be more friendly.  And if done right it will also show each of us some things that are missing.