═══ 1. Overview ═══

PartMeister is a component wizard for generating OpenDoc parts. 


═══ 2. Menu Selections ═══


═══ 2.1. Part menu ═══

The part menu contains items for managing actions that act upon the current 
application workspace. 


═══ 2.1.1. Generate ═══

Generates an OpenDoc part based on the current workspace information. 


═══ 2.2. Template menu ═══

The template manu contains items for managing the set of available templates. 


═══ 2.2.1. Add ═══

Add a new template to the current set. Not available in this release. 


═══ 2.2.2. Remove ═══

Remove a new template to the current set. Not available in this release. 


═══ 2.3. Help menu ═══

The help menu provides access to information to assist the user in learning and 
using the application. 


═══ 2.4. Help index ═══

Index of help topics. 


═══ 2.5. General help ═══

General overview of the application and its function. 


═══ 2.6. Using help ═══

Guide to using the help system. 


═══ 2.7. Product information ═══

Display product name and copyright information. 


═══ 2.8. Template ═══

The selected template determines what files are generated and the content of 
the files. Templates use the information provided by the user to create custom 
components based on the values entered. 

Templates may be added or removed from this list using the menu options 
available on the Template menu. 

For information on creating your own templates, see the User's Guide (VIEW 
PMEISTER). 


═══ 2.9. Class name ═══

The class name is used as the SOM class name for the component. 


═══ 2.10. Short name ═══

A short name, from 1 to 8 characters, is required for generating file names - 
as the FAT file system imposes this limitation.  Only valid characters for a 
file name may be used (ie. no spaces). 


═══ 2.11. Category ═══

Categories are defined by CI-Labs, or created by the part developer, to 
indicated the general data type for a part.  A list of defined categories is 
provided in the drop-down list or you may type your own. 


═══ 2.12. Kind ═══

Kind refers to the specific data type, for instance the format of data for a 
specific word processor. 

A common format for kind is Company:Kind:ClassName for unique data types (ie. 
IBM:Kind:MyPart). 


═══ 2.13. Display name ═══

During registration, OpenDoc requests a display name from the part. This name 
will be returned. 


═══ 2.14. Author name ═══

In the header information for each source file, the author line will contain 
this name. 


═══ 2.15. Company name ═══

In the header information for each source file, the copyright line will contain 
this name (ie. Copyright (c) 1995, ABC Inc). 


═══ 2.16. Copyright years ═══

In the header information for each source file, the copyright line will contain 
these years (ie. Copyright (c) 1995-1996, ABC Inc). 


═══ 2.17. IBM C Set ++ for OS/2 compiler ═══

If you will be using the IBM C Set++ for OS/2 compiler, select this. This 
choice only affects the makefile. 


═══ 2.18. IBM VisualAge C++ for OS/2 compiler ═══

If you will be using the IBM VisualAge C++ for OS/2 compiler, select this. This 
choice only affects the makefile. 


═══ 2.19. Runtime directory ═══

The runtime directory specifies the location of the OpenDoc runtime (the user 
runtime). The makefiles shipped with PartMeister copy the DLL generated to the 
BIN directory of the runtime after a successful build. 


═══ 2.20. Toolkit directory ═══

The toolkit directory specifies the location of the OpenDoc toolkit (ie. 
C:\TOOLKIT). 


═══ 2.21. Public directory ═══

The public directory is the location where all files that are used by more than 
one component are stored. For example, any part that may be used as a 
superclass should have its IDL, XH and LIB files stored in the public 
directory. 

It is recommended that you create a new public directory in a directory that is 
created specifically for creating OpenDoc parts (ie. C:\ODPARTS\PUBLIC). 


═══ 2.22. Output directory ═══

When a part is generated, a subdirectory will be created inside this directory 
(using the short name). All source files generated will be created inside the 
new subdirectory. 

It is recommended that you create a new directory specifically for creating 
OpenDoc parts, and specify that directory here (ie. C:\ODPARTS). 


═══ 2.23. Product Info ═══

Displays application, copyright and support information. 

Click the Close pushbutton to dismiss the dialog.