Knowledge workbenches provide you with different ways to define "pseudo applications" or sets of features. Even if these applications are not C++ developed, they need to be managed like any classic C++ application. A new directory created to ease the managing of these applications and features will help you in this task. This management can be performed using a new environment variable, and a new setting, and possibly the RADE tools.
Knowledge products can rely on the following Knowledge resources:
.CATfct files generated by BKT and reused by BK2 products contain types, functions, methods, and exposed main behaviors.
The index is used by the Knowledgeware Index and is used in the Knowledge language, in Knowledge Expert or in BKT.
.CATGscript files are generated in the User Feature type definition tab, and reused by the Knowledge index to build a complete view of the Knowledge dictionary of types.
Application Resource Management .catalog files establish a link between a logical name of a resource and the physical resource referenced through the catalog. The objective of those catalogs is to answer this simple question: "give me the object named XXX". This is possible in BKT using the Instantiate Template, the Load, the Knowledge Certify and the Insert Component behaviors. It is also used in PKT by the Knowledge Pattern feature.
Knowledge Resources can include many kinds of data used as resources in the
Knowledge language or in BKT like CATPart, CATProduct and .catalog documents.
If the user wants to open a .CATPart file and indicates the name of the file, the system will try to find this file in the
directory first. If he indicates an ARMCatalogName|Resource name, and if:
|=> it will try to find the resource in this directory.|
The Workbenches file called WBIM.xml is generated by BKT. It contains the local User categories and the Deployed workbenches definition.
.CATNls files are used by BKT applications, by the User Features, the BuildMessage functions, and the tool tips translations to:
BuildMessageNLS("CATKneTestCatalog","Zero"))looks for the CATKneTestCatalog.CATNls file and tries to translate the Zero keyword.
CATVBA and .CATScript macros, edited in the CATIA macro editor or any editor, are reused by different Knowledge products:
Icons associated to User Features and BKT Technological objects and
behaviors are located in the