<> <> <<>> <<1. The Structure of Cedar>> by Dan Swinehart, Polle Zellweger, and Bob Hagmann <<2. Overview>> The Cedar Family Tree A Pictorial Tour of Cedar The Structure of a Cedar Application A Program-Development Example <<3. The Cedar Family Tree>> [Evolution of Cedar picture] <<4. What Cedar has inherited>> Programming support, document composition, and information management for personal computers in a network environment One programming language, operating in a single address space Open architecture System routines are ordinary procedures and functions Components at any level are available to all higher levels <<5. What's New about Cedar>> Automatic storage-management and runtime types for a strongly-typed language Memory-management tuned for large virtual and physical memories Key components availabile to most system and application packages Support for integration of user applications <<6. House of Cards Slide>> [S of C picture] <<7. Cedar Machine Division>> [Cedar Machine] <<8 Nucleus Division>> [Nucleus] <<9. Life Support Division>> [Life Support] <<10. Applications Division>> [Applications] <<11. The Structure of a Cedar Application>> [Shows two user interfaces using a single package, the package using a particular lower-level package, and everybody using the standard low-level goodies. ] <<12. 2d part of same>> [Shows one of the two user interfaces including its own package and bypassing to one of the lower.] <<>> <<13. Tioga/Viewers Example>> [Shows the H of C, with Commander, Tioga, Viewers, TIP, Inscript, Cedar Graphics highlighted, using lower-level goodies.] <<14. New/Old Viewers Example>> [The world-famous slide] <<15. Summary -- Cedar as an Open Architecture -- need help!>> Summary Inherited Characteristics: Calls among components must satisfy partial ordering Components are available to clients at all higher levels Components can be bound within firewalls Added Characteristics: Automatically-managed storage reduces programming effort Runtime types support many program-management techniques Vital components widely available due to low-level placement Remote Procedure Call makes remote applications directly available Attention to integration Qualitative improvement in programming productivity <<16. The Cedar Metafive>> [Picture]