Importing components
This chapter describes how to import (copy) VA Smalltalk components from one library to another.
Importing enables you to copy entire components. When you import components, they retain version names, ownership settings, queries, comments, and so on. These are not retained when you file in components. Importing also enables you to do the following:
•Load components faster than file-in operations
•Create small backup files of selected components
•Maintain versions across multiple libraries
•Create new libraries that hold selected versions (unlike cloning a library, which copies all versions to the new library)
The types of components that you can import include the following:
•User objects
•Classes
•Applications (or subapplications)
•Configuration maps
Last modified date: 01/29/2015