|
|
Sample Programs from NeXSTEP 3.3
{\rtf0\ansi{\fonttbl\f0\fswiss Helvetica;\f1\fmodern Ohlfs;}
\paperw11440
\paperh11780
\margl120
\margr120
{\colortbl;\red0\green0\blue0;}
\pard\tx1600\tx3200\tx4800\tx6400\tx8000\tx9600\tx11200\tx12800\tx14400\tx16000\f0\b0\i0\ulnone\fs72\fc0\cf0 DataSource.app\
\fs24 SHL Object Technology Center\
e-mail: [email protected]\
\
\
\
\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\b\fs36\fc0\cf0 Overview
\b0\fs24 \
\
\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\fc1\cf1 This example demonstrates how you can implement a custom data source by creating an object that conforms to the EODataSources protocol. From an EOController perspective (UI layer), a persistent store (ie. a database) is not required, just an object that conforms to the EODataSources protocol. Thus you can take advantage of the features found in EOController (buffering, undo, etc) without having a real database by implementing a custom data source.\
\
\fc0\cf0 NEXTSTEP 3.2 and EOF Release 1.0\
\fc1\cf1
\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fc1\cf1 \
\
\
\b\fs36 Program Organization
\b0\fs24 \
\
\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\i\fc1\cf1 Important Files
\i0 \
\
DataSource.[hm] conforms to the EODataSources protocol.\
Motorcycle.[hm] is the class of objects provided by the data source.\
Images (folder) contains some motorcycle images you can use for inserts / updates.
\pard\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fi-1900\li1900\fc1\cf1 \
\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\fc1\cf1 \
\pard\tx1140\tx2300\tx3440\tx4600\tx5760\tx6900\tx8060\tx9200\tx10360\tx11520\fc1\cf1 \
\b\fs36 Revision History
\b0\fs24 \
\
June 94 Version 1.0.\
}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.