CONTIBUTOR: Riley Rainey Atria Software e-mail:riley@atria.com ====================================================== ********************************************************** ************** THIS IS UNSUPPORTED SOFTWARE ************** ********************************************************** ********************************************************** * Atria makes no representation that the descriptions * * and software code contained in this document will * * not infringe on existing or future patent rights, * * copyrights, trademarks, trade secrets or other * * proprietary rights of third parties. The * * descriptions contained herein do not imply the * * granting of licenses to make, use, sell, license or * * otherwise transfer Atria products described herein. * * Atria disclaims responsibility for errors which may * * appear in this document, and it reserves the right, * * in its sole discretion and without notice, to make * * substitutions and modifications in the products and * * practices described in this document. * ********************************************************** ----------------------------------------- T0010: Frame Book Trigger ----------------------------------------- Framemaker books are actually one or more Frame documents glued together logically by a top level book file. This trigger allows users to handle all parts of a book as a logical unit. It works by scanning the book file to dynamically determine component documents. Checkouts, checkins, and uncheckouts of the `book' file automatically generates an appropriate action for each document. To install the management of frame books, perform these steps: o set a view; cd to any directory in the VOB o type: $ frame_book_trigger -install This will create a new element type, "frame_book" and installs this trigger so that it will take special actions as checkout, checkin, and uncheckout time. o Set the element type on any Frame books that you have under version control: $ cleartool chtype frame_book foo.book You are now ready to go. When a book file is modified, the component frame documents are managed automatically. For example, at checkout time all component documents will be checked-out with the book file. At checkin, modified documents will be checked-in and all others will be "unchecked-out".