CDExtrasDoc.tioga
Christian Jacobi, November 29, 1985 1:01:28 pm PST
Christian Jacobi, February 25, 1986 10:30:09 am PST
CDExtras
CEDAR 6.0 — FOR INTERNAL XEROX USE ONLY
CDExtras (ChipNDale Extras)
Christian Jacobi
© Copyright 1985, 1986 Xerox Corporation. All rights reserved.
Abstract: Extras for CD implementors
Created by: Christian Jacobi
Maintained by: partly: Christian Jacobi <Jacobi.pa>
Keywords: ChipNDale
XEROX  Xerox Corporation
   Palo Alto Research Center
   3333 Coyote Hill Road
   Palo Alto, California 94304

For Internal Xerox Use Only
A. Useful for designers creating designs by program
1. CDUtil
Handy procedures for creating designs from programs. Abuts, Conditional instances...
2. CDDynamicObs
Object class which consists of code (Generators); will be regenerated whenever some constituent does change. Useful to debug program generated designs.
Start: CDDynamicObs.load
Creation of dynamic generator environment: <space-U> menu and select create dynamic generator.
3. CDCleanUp
Handy procedures for creating designs with lazy programs. Lazy programs might simply build objects without including them into the designs directory, but call CleanUp before the design is handed to any other usage. (I'm not sure if I will maintain this, but I certainly will keep the source)
Start: Not necessary, CDCleanUp is resident with ChipNDale
Interactive call: "check directory" in the special commands pop up menu. Programs generating layout the lazy way are supposed to call the clean up procedure and must NOT rely on interactive calls, except for debugging.
B. Mainly for tool makers
4. CDFeedback
Feedback module from Mike for Spinifexes Rosemary output. Not maintained by Christian.
5. CDX
Some coordinate system transformations.
6. CDSomeImplementors
Implementing client origin for certain object classes. Useful for object class implementors.
7. CDBottomUp
A module which allows easy implementation of bottom up calls which cache the results.
Each independent call creates a new invocation key. Results which are created with the same invocation key are allways trusted and taken from the cache. Results with a different invocation key are re-used if all the subcells haven't changed