|
|
1.1 ! root 1: {\rtf0\ansi{\fonttbl\f0\fswiss Helvetica;\f1\fmodern Ohlfs;} ! 2: \paperw11440 ! 3: \paperh12580 ! 4: \margl120 ! 5: \margr120 ! 6: {\colortbl;\red0\green0\blue0;} ! 7: \pard\tx1600\tx3200\tx4800\tx6400\tx8000\tx9600\tx11200\tx12800\tx14400\tx16000\f0\b0\i0\ulnone\fs72\fc0\cf0 EnterpriseObject.app\ ! 8: ! 9: \fs24 SHL Object Technology Center\ ! 10: e-mail: [email protected]\ ! 11: \ ! 12: \ ! 13: \ ! 14: ! 15: \b\fs36 Overview ! 16: \b0\fs24 \ ! 17: \ ! 18: ! 19: \fc1\cf1 This example demonstrates how you can implement a custom enterprise object and map it and its attributes to the database. In this example, the class Author is mapped to the authors entity in the Sybase pubs database through the EOModeler app. The EOKeyValueCoding protocol (informal) is then implemented to transfer values to and from the object and database.\ ! 20: \ ! 21: ! 22: \fc0\cf0 NEXTSTEP 3.2 and EOF Release 1.0 \ ! 23: Sybase Adaptor \ ! 24: ! 25: \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\fc0\cf0 pubs Database\ ! 26: ! 27: \pard\tx1600\tx3200\tx4800\tx6400\tx8000\tx9600\tx11200\tx12800\tx14400\tx16000\fc1\cf1 \ ! 28: \ ! 29: \ ! 30: ! 31: \b\fs36 Program Organization ! 32: \b0\fs24 \ ! 33: \ ! 34: ! 35: \i Important Files ! 36: \i0 \ ! 37: \ ! 38: Author.[hm] is our enterprise object.\ ! 39: Author.eomodel contains binding information and is created by EOModeler.app.\ ! 40: \ ! 41: \ ! 42: \ ! 43: ! 44: \b\fs36 Revision History ! 45: \b0\fs24 \ ! 46: \ ! 47: June 94 Version 1.0.\ ! 48: ! 49: }
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.