The old school guys are hard enough to keep within a standard routine of doing things.
I would likely have to manage the whole process for them transparently, they wont understand let alone care.
If annotative & dimscale worked together I wouldn't have to go out of my way relying on dimscale.
Unfortunately with the two completely separate, a complete interface redesign is required including the block libraries.
I just can't see any gains or benefit in the interface time invested.
Its bad enough having to re-write documentation with interface changes every year now.
Not to mention actually trying to make cost effective productivity customizations on my own.
What I have done with the 2009 interface so far in deployment was trim all the fat out.
Nobody cares about the ribbon so I disabled it.
Hiding the pulldowns,
adding all of the standard items to the quick access toolbar,
having the layer manager as a flyout palette,
adding a listing of all our customizations in organized menus available to use the Search menu feature,
quick properties,
Using the ACAD.cui instead of the MEP.cui for the networked implementation.
Everyone that has seen the new interface wants it.
It loads faster and does what they want it to do.
The workspace is considerably cleaner as well.
The only major failure point; aecSelectSimilar.
Major productivity tool. Autodesk needs to put out the code for this feature in Vanilla period.
Works on nearly anything the way 90% of us need it to and better than qselect.
Not to mention so convenient!
I can't get it written in lisp to work anywhere close as well let alone transparently like it does in MEP.
