April 25, 2011 02:17 PM
(in response to COE Administrator)
These two questions are very similar and can be answered
C++ APIs as well as automation APIs have undergone changes between
V5 and Version 6. There will be a Version 6 adoption effort that
can range from very easy (part-level only macro for instance) to
more complex (electrical, product-related for instance). Yet, the
language, technology, and tools remain the same and early adopters
can adopt V6 with limited effort.
Most complex changes reflect the integration with the collaborative
environment and the customizable database as illustrated by these
- “CATDocument” /”CATIADocument” classes
are replaced by other patterns.
- To create data, you need to get the mandatory attributes set the
customer company has decided to have; if you’re a partner,
your code should be customization neutral.
Some other changes in the C++ APIs are architecture-related. In
such cases, there is almost always a one-to-one mapping and we have
tools to help with adoption, for instance:
- Geometric modeler encapsulation allows building smaller products
such as 3D Live.
- Separating “Standard” APIs from the
Adoption patterns for CATIA V5 APIs are documented in both the C++
and Automation V6 encyclopedia in the “V6 adoption”
section. The Automation encyclopedia is part of any Version 6 CATIA
installation (DSYAutomation.chm file). An automated tool to audit
V5 code is available, allowing Version 6 adoption project
feasibility and sizing evaluation. It is recommended to run this
tool on the V5R20 code. Trainings for Version 6 adoption are also