2012
Table Of Contents
- Contents
- Basic Customization
- Overview of Customization
- Organize Program and Support Files
- Customize a Publish to Web Template
- Define Custom Commands
- Record and Modify Action Macros
- Custom Linetypes
- Custom Hatch Patterns
- User Interface Customization
- Understand User Interface Customization
- Work with the Customize User Interface (CUI) Editor
- Create and Manage Customization Files
- Customize Commands
- Overview of Commands
- Create, Edit, and Reuse Commands
- Create Macros
- Overview of Macros
- Use Special Control Characters in Macros
- Pause for User Input in Macros
- Provide International Support in Macros
- Use Built-in Commands in Macros
- Repeat Commands in Macros
- Use Single Object Selection Mode in Macros
- Use Macros to Swap User Interface Elements
- Use Conditional Expressions in Macros
- Use AutoLISP in Macros
- Control the Display of Command Items
- Assign Search Tags
- Create Tooltips and Extended Help for Commands
- Create Status Line Help Messages
- Create and Manage Images for Commands
- Customize User Interface Elements
- Load an AutoLISP File
- Customize Workspaces
- Transfer and Migrate Customization
- Customize User Interface (CUI) Editor FAQs
- DIESEL
- Slides and Command Scripts
- Introduction to Programming Interfaces
- Shapes and Shape Fonts
- Overview of Shape Files
- Create Shape Definition Files
- Shape Descriptions
- Vector Length and Direction Code
- Special Codes
- Use Special Codes
- Codes 0, 1, and 2: End of Shape and Draw Mode Control
- Codes 3 and 4: Size Control
- Codes 5 and 6: Location Save/Restore
- Code 7: Subshape
- Codes 8 and 9: X-Y Displacements
- Code 00A: Octant Arc
- Code 00B: Fractional Arc
- Codes 00C and 00D: Bulge-Specified Arcs
- Code 00E: Flag Vertical Text Command
- Text Font Descriptions
- Sample Files
- Big Font Descriptions
- Unicode Font Descriptions
- Superscripts and Subscripts in SHX Files
- Migrate and Transfer Custom Settings and Files
- Index
The information contained in the file can be used to specify which
AutoCAD-based products and releases the plug-in can be loaded into, their
supported Operating System, and how the application should be loaded, such
as load on startup or when a command is invoked.
The following elements are used to define and describe the plug-in:
■
ApplicationPackage on page 452
■ CompanyDetails on page 454
■ Components on page 455
PackageContents.xml for Download versus Local Deployment
How you plan to deploy your plug-in determines what should be in the
PackageContents.xml file. You need to supply more information when
providing a plug-in for download versus a local deployment. The following
table explains which elements and attributes are required, optional, or
recommended for the deployment you want to use.
For Local Deploy-
ment
For Download from
the Apps tab on
Autodesk Exchange
ApplicationPackage element
RequiredRequiredSchemaVersion
RequiredRequiredAppVersion
OptionalRequiredAuthor
RecommendedRequiredName
RecommendedRequiredDescription
RecommendedRequiredIcon
RecommendedRequiredHelpfile
RequiredRequiredProductCode
OptionalRequiredUpgradeCode
CompanyDetails element
450 | Chapter 7 Introduction to Programming Interfaces