22 164.000000 356.000000 7 Caption A 10 A 20 A B 56 /khare/Library/eText/Pages.etfd/Untitled-2013734902.tiff 24 Untitled-2013734902.tiff¬
eText: Document-Based Object Processing
vs.
Pages: Object-Based Document Processing
22 128.000000 446.000000 7 Caption A 10 A 20 A B 56 /khare/Library/eText/Pages.etfd/Untitled-2109684881.tiff 24 Untitled-2109684881.tiff¬
A presentation for Pages Software, Inc. · January 13, 1994
10 ¬Introduction
What is eText?
	Project Goals
10 277d27f7 5 Goals 0 ¬	eText is really about managing objects and happens to use a document model; Pages manages documents and happens to use an object model.
277d27f7 ¬
	Mission Statement	
10 12817664 7 Mission 0 ¬	eText is an extensible, document-based WYSYIWG hypermedia authoring system.
12817664 ¬
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