*Title: wotonomy user guide: control package

*TOC

* Introduction

** Scope

This document is intended to serve as a Java developer's introduction to the wotonomy control framework and how to use it to back an application built with the wotonomy ui or web frameworks with data from a database or other persistent storage mechanism.

** Overview

The wotonomy classes contained in the net.wotonomy.control package provide nestable editing buffers that decouple the model portion of your application from any specific persistence mechanism.  

*** Where does it fit in?

The control package supports both the ui and web packages.  Both ui and web packages can be used without the control package, but the control package enhances both significantly.  The point of contact is the EODataSource, which can be used to populate both EODisplayGroups and WODisplayGroups.

But aside from the EODataSource, the ui and control packages work in parallel.  The data model objects that are observed by a display group are also observed by an editing context.  The edi

 - EOObjectStore
   - abstract class: encapsulates something to save changes to
   - while you will work almost exclusively with editing contexts, most of the methods you will call are defined in object store.
   - getting data

   - data objects are specific to the type of object store
   - faulting

 - EOEditingContext
   - parent is object store
   - supports all methods of object store
   - additional methods
     - saveChanges
     - hasChanges
     - insertedObjects
     - updatedObjects
     - deletedObjects

   - object graph / edit buffer / in-place editing
   - versioning of objects
   - observes objects / maintains lists

 - NSNotificationCenter
   - Notifications
   - Subscribing
   - Posting
     - Center
     - Queue

   

 - EODataSource
   - bridge between ui and control