| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (9 out of 10)

Saving an Image with a KB

The Save-image-data-with-kb attribute of an image definition determines whether the image file is saved as part of your KB. The default for this attribute is no. Change this attribute to yes to save the image as part of your KB.

Advantages and Disadvantages

As a general guideline, you will probably not want to save image files with your KB during development, since changes to the image file will not be reflected in the KB. Note that any KB that requires an image file, but does not save the image with the KB, is inherently incomplete.

Saving an image file with your KB protects the integrity of the image file for deployment purposes, and ensures that the KB is complete. However, the size of your KB will increase by significantly more than the size of the image file because:

If KB size is an issue, you may not want to save image files with the KB.

Deploying a KB without saving its images requires that you determine an appropriate directory location for the image files to be stored at a customer site. Since directory specifications are operating-system specific, you can increase KB portability by saving the image with the KB. Also, consider the fact that image files in a directory at a customer site are subject to change and deletion.

Omitting the Pathname of an Image Saved With a KB

If you specify a valid image definition, then use the Save-image-data-with-kb attribute to save the image with the KB, you can thereafter change the definition's File-name-of-image attribute to be none. G2 knows that the image has been saved in the KB, and therefore does not describe the image definition as incomplete in its Notes attribute, as it would if no pathname were specified and no image had been saved.

| Prev | Next | Start of Chapter | End of Chapter | Contents | Glossary | Index | Comments | (9 out of 10)

Copyright © 1997 Gensym Corporation, Inc.