Summary of Customization Procedures

Summary of Customization Procedures

This document examines the various customization procedures in detail. The following table summarizes how customizations are accomplished:

 
Type of Customization Where Data Goes  Tell Builder Xcessory How To Use Data 
New widgets  In a library, loaded dynamically from the shared library path or linked with thebx.o file.  Primarily use a WML file and other control files. For systems running SunOS 4 (or other systems where a shared library is unavailable), also must link bx.o with a file providing functions making calls to extend Builder Xcessory. 
New ViewKit or
UI components
In a library, loaded dynamically from the shared library path.  Primarily use a WML file and other control files. Components cannot be added on systems running SunOS 4. 
New Resource Editors  In a library, loaded dynamically from certain Builder Xcessory areas or linked with the bx.o file.  Use extra functions linked to the library making calls to extend Builder Xcessory. On systems running SunOS 4, use those functions linked into the bx.o file. 
New Callback Functions  In a library, loaded dynamically from certain Builder Xcessory areas or linked with the bx.o file.  Use extra functions linked to the library making calls to extend Builder Xcessory. On systems running SunOS 4, use those functions linked into the bx.o file. 
 

 

Documentation: