OPENSTEP 4.2  Copyright1997 by Apple Computer, Inc.  All Rights Reserved.

Release Notes: 
Enterprise Objects Framework 2.1

This file describes new product features and explains how to install the examples. It does not contain complete release notes for prerelease 2.1 of Enterprise Objects Framework. Complete release notes will be made available when the product is released.

For the 2.0 release notes (which include a lot of information that's still relevant for 2.1), see NeXTanswer #2455. If you have access to the World Wide Web, you can look up the URL http://www.next.com/NeXTanswers/HTMLFiles/2455.htmld/2455.html.

The documentation supplied with this release is 2.0 documentation. The 2.1 documentation will be made available when the product is released.

The MachOS version of this release is 3-way fat; it can be used to develop software for NeXT, Intel, and SPARC. The OpenStep for Windows version of this release can be used to develop software for Intel machines running Windows NT.

New Features for 2.1

·	You can add methods to your interface in Interface Builder to perform queries and calculations on a specified class property.

·	You can associate a qualifier with a display group in Interface Builder.

·	Interface Builder allows you to set a fetch limit.

·	You no longer have to add key paths as strings in Interface Builder-- instead, you can traverse the object graph in the Inspector to connect to the desired property.

·	There is a new EOComboBoxAssociation.

·	There is a new EOArrayDataSource class.

·	EOModeler has a new "Explorer" outline interface that makes model traversal easier.

·	When you connect a control to a display group in Interface Builder, a formatter is automatically added to the control based on the associated property's data type.

·	There is a new Enterprise Objects Framework wizard that automates the creation of simple Enterprise Objects Framework applications. When you create an application in Project Builder, you have the option of either creating a conventional Enterprise Objects Framework application or using the wizard to automate application creation.

·	EOModeler provides an Inspector for editing the connection dictionary.

·	The Diagram View in EOModeler, formerly just an example, is now a part of the product.

·	The Enterprise Objects Framework examples have been updated.

·	The Oracle and Informix adaptors link with the newest client libraries.

·	The new Oracle login panel is designed to work with SQL*Netv2.

Installing the Examples

This release provides on-line examples to help familiarize you with Enterprise Objects Framework 2.1. These examples are located in /NextDeveloper/Examples/EnterpriseObjects. Installing the examples involves these steps:

·	Setting up users and databases on your database server for the example databases.
·	Installing the example directory.
·	Populating your database server with example data.

Note: When installing the examples for use with the Informix adaptor, use EOModeler's Connection Dictionary Inspector to set "databaseEncoding" to "Non-lossy ASCII" for the Movies and Rentals models. This will allow Enterprise Objects Framework to insert records with non-English characters.

Setting up Database Accounts

The Enterprise Objects Framework 2.1 examples use two sets of tables: Movies and Rentals. Some examples use just one of the these databases, while others use both. The multi-database support in Enterprise Objects Framework 2.1 makes it possible for you to install these databases in three different configurations:

·	Both sets of tables together in a single user/database.
·	Each set of tables in its own user/database on the same database server.
·	Each set of tables on its own database server (for example, Movies on Informix, Rentals on Oracle).

Depending on your desired setup, you use the tools available with your database server to set up one or two new user/databases. For example. on Sybase you might create a new database on your server called ªMoviesº and login with the user ªsaº. On Oracle you might create a new user with the name ªMoviesº. Once you have set up these accounts, you're ready to install the examples. 

Copying the Example Directory

To configure and build the examples you need to copy the example directory to a writable area in your file system. You can do this by copying the /NextDeveloper/Examples/EnterpriseObjects folder into your home directory (or any other directory writable by you).

Configuring the Example Models

The model files used by the examples must be configured to use your adaptor and server. To configure the examples, run the configure_examples program in your copy of the examples directory. It will ask you for the name of the adaptor you wish to use (Informix, Oracle, Sybase, and so on) and for the login information for your database. It will then convert the example models for your server.

Populating the Databases

Now that the examples are configured, you can fill your example databases with sample data. The install_database tool in the DatabaseSetUp directory will connect to your databases, add the example tables, and fill them with data. If you later wish to remove the data, simple run the drop_database tool.

Building the Example Programs

With your example projects installed and your database filled with data, you are ready to build and run the examples. To do this, in a command shell cd to your example directory and type make all. This performs a make install on BusinessLogic.framework and EOExtensions.framework to put them in /LocalDeveloper/Frameworks, where they are shared by many of the other examples. It then makes all of the examples applications.

Note: The /LocalDeveloper/Frameworks directory must be created and writable by you in order to build the examples. On Mach this can be accomplished by using su to become the superuser and then executing the following commands:

mkdirs /LocalDeveloper/Frameworks
chmod a+w /LocalDeveloper/Frameworks