Managing the AutoCAD ® CUI, Empowering the Users

1. Managing the AutoCAD® CUI, Empowering the Users R. Robert Bell Design Technology Manager, Sparling

2. This Course is Right for You If… • CUI means Can’t Understand It • Workspace is a cubical • Your users are revolting • Enterprise is a ship and not something in AutoCAD

3. R. Robert Bell • Design Technology Manager at Sparling since 2007(largest US electrical specialty firm) • Former network administrator at an MEP firm for 19 years • Writing code since 1983 • Former AUGI Director • Self-admitted Autodesk/AUGI discussion group junkie • Active participant in Autodesk Beta Programs • Published author

4. Getting to Know You • How many have deployed AutoCAD 2006 or later? • Is the CUI one of the reasons you haven't upgraded? • How many have deployed AutoCAD 2009 or later? • How many are comfortable editing menu macros? • How many have used the CUI? • How many need to support multiple verticals?

5. Terms • CUI and CUIx • Main • Enterprise • Partial CUIx • Core CUIx • Office CUIx • Nodes • Workspace • Commands • Vertical

6. CUI Organization, the Issues • Enterprise • Workspaces • New UI elements • Ribbon • Quick Access Toolbar • Quick Properties • Rollover Tooltips • Temporary overrides • Double-click actions • CUIx files "remember" what files are partial to them

7. Main, Enterprise, and Partial CUIx • Main CUIx file • Directly add new commands • Stores user’s modifications • Workspaces available • Enterprise CUIx file • Read-only in the current profile, including partials • Workspaces available • Partial CUIx file • Any CUIx file loaded into either the main or enterprise CUIx files • May have a few nodes, or many

8. Load Order and Precedence Enterprise Enterprise partials (in order) Main Main partials (in order) • Last loaded keyboard shortcuts, double-clicks, and quick properties win • All other elements the first loaded instance wins • All shortcut menus load from one file

9. Main CUIx Considerations • What is important to you? • “Protect” the core files? • Multiple verticals? • Multiple users? • Office standards • Enterprise protects your standards, protect it • Workspaces • How do you plan to roll out new/modified ones? • Main must be editable by user

10. What File Should Be Main? • Core • Too easy to delete elements • How many times do you want to restore the file(s)? • Copy of core • How would you get to standard interface elements? • Copy of office CUI • Get real! • Custom • Missing non-transferable elements • New, blank CUI • Create via Transfer tab

11. Enterprise CUIx Considerations • The options can overwhelm • In fact, the choice is obvious • Need a file for tools that work in all verticals • Need a file for tools specific to a vertical • Workspaces • Need to always provide the core file(s) • Workspaces • Load order plays a role

12. What file should be Enterprise? • One factor drives decision: • Workspaces • Workspaces must control UI elements for specific verticals • Workspaces must be controlled, at some level, by the CAD Manager • Workspaces are only available at main or enterprise • A "vanilla" file cannot control multiple verticals

13. Office Vertical Considerations • Workspaces

14. The Ramifications • Structure is more fragmented • Vertical flavored office "root" • Non-specific office items • Vertical file(s) • Add-ons • Main CUI is a blank slate for the users

15. File Locations • The same as it's always been • User files where they can modify • Office files on network, read-only • OOTB files • How paranoid (or busy) are you? • Support path effect

16. Backup • Backup • Backup before editing (zip file archives) • 2007 introduced Restore/Reset • Save your workspace • Latest Updates (2009)

17. The Editor

18. CUI Editor Demonstration

19. Summary • New user interfaces are only available via the CUI • Migration can be painless • Workspaces play large role • Enterprise is the mechanism to support workspaces • Vertical applications require vertical support • Planning your structure will pay off • Do not over-think the CUI editor