This is TXT.rtf in view mode; [Download] [Up]
eText: Document-Based Object Processing vs. Pages: Object-Based Document Processing A presentation for Pages Software, Inc. · January 13, 1994 Introduction What is eText? Project Goals eText is really about managing objects and happens to use a document model; Pages manages documents and happens to use an object model. Mission Statement eText is an extensible, document-based WYSYIWG hypermedia authoring system. How is it like Pages? Extensible Compound Document Framework Complete WYSIWYG UI Same Undo Framework Pasteboard-Driven Dataflow How does it differ? Articulation vs. Filtering Component-driven parsing & generation Formatting vs. Tagging Projecting visual cues into logical structure Behavior vs. Structure eText objects are completely defined by behavior; Pages objects can support internal structure (trees, lists) Native hypertext features Navigation and hyperlinking as integral notions Directions: eText HTML Input Agents oSpace Visualizing Object Processing Directions: Pages tikORP The Inverse Kit for Objects Residing in Pages Ð Ernest N. Prabhakar Pages as integrating platform How compelling is Pages as a universal container. Structure-Driven Workflow i.e. ªEnterprise-Objectº-Based Document Processing Integration Intiatives Pasteboard Types URL/URI Type HTML text type Extended entity maps nögi advocacy Seals of Approval? User-driven standards Interapplication Linking ªManaged HTMLº Shared DocInfos
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.