--- a/AspctAdptr.st	Thu May 02 11:57:36 1996 +0200
+++ b/AspctAdptr.st	Thu May 02 15:28:28 1996 +0200
@@ -39,12 +39,16 @@
     from/to a complex model.
 
     Consider the case where editFields are required for the
-    elements (instance variables) of a more complex model.
-    Without an aspect adaptor, you needed to copy the individual
-    values out-of and into multiple valueHolders.
+    elements (instance variables) of a compound object;
+    - without an aspect adaptor, you needed to copy the individual
+      values out-of the object and move these into multiple valueHolders.
+      Then, let the editFields modify the valueHolders contents and
+      finally, fetch the values and put them back into the compound object.
+
     An aspectAdaptor makes this easier, by playing model with
     value/value: symbols towards the editField, and forwarding changes and
-    updates to/from the complex model using different aspect symbols.
+    updates to/from the combound object using different aspect symbols
+    and access messages.
 
     Notice: 
         this class was implemented using protocol information
@@ -236,5 +240,5 @@
 !AspectAdaptor class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libview2/Attic/AspctAdptr.st,v 1.12 1996-04-27 17:58:52 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libview2/Attic/AspctAdptr.st,v 1.13 1996-05-02 13:27:47 cg Exp $'
 ! !

--- a/AspectAdaptor.st	Thu May 02 11:57:36 1996 +0200
+++ b/AspectAdaptor.st	Thu May 02 15:28:28 1996 +0200
@@ -39,12 +39,16 @@
     from/to a complex model.
 
     Consider the case where editFields are required for the
-    elements (instance variables) of a more complex model.
-    Without an aspect adaptor, you needed to copy the individual
-    values out-of and into multiple valueHolders.
+    elements (instance variables) of a compound object;
+    - without an aspect adaptor, you needed to copy the individual
+      values out-of the object and move these into multiple valueHolders.
+      Then, let the editFields modify the valueHolders contents and
+      finally, fetch the values and put them back into the compound object.
+
     An aspectAdaptor makes this easier, by playing model with
     value/value: symbols towards the editField, and forwarding changes and
-    updates to/from the complex model using different aspect symbols.
+    updates to/from the combound object using different aspect symbols
+    and access messages.
 
     Notice: 
         this class was implemented using protocol information
@@ -236,5 +240,5 @@
 !AspectAdaptor class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libview2/AspectAdaptor.st,v 1.12 1996-04-27 17:58:52 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libview2/AspectAdaptor.st,v 1.13 1996-05-02 13:27:47 cg Exp $'
 ! !

--- a/Model.st	Thu May 02 11:57:36 1996 +0200
+++ b/Model.st	Thu May 02 15:28:28 1996 +0200
@@ -35,22 +35,33 @@
 
 documentation
 "
-    Models are things that are presented in views. Instances keep track of 
-    which views are dependent of them and inform them of any changes.
-    Actually the Model class is not really needed; since the dependency
-    mechanism is inherited by Object, you can take any object as a model.
-    However, instances of Model (and subclasses) keep the dependents locally
-    in an instance variable; thus speeding up access a bit.
+    Models are things which represent information models, i.e. something
+    which holds the data for user interface components and on which these operate.
+    Basically, instances keep track of which components depend on them and 
+    inform the dependents of any changes.
+
+    The Model class itself is abstract and not too useful, see subclasses,
+    especially, ValueHolder and SelectionInList.
+
+    Notice:
+      Actually the Model class is not really needed; since the dependency
+      mechanism is inherited by Object, you can take any object as a model.
+      However, instances of Model (and subclasses) keep the dependents locally
+      in an instance variable; thus speeding up access a bit.
 
     [Instance variables:]
-        dependents      Collection      those objects which depend on me.
-                                        To save some storage, the dependent is
-                                        kept directly here, IFF there os only one.
-                                        Otherwise, a collection of dependents is
-                                        held here.
+        dependents      <Collection>    those objects which depend on me.
+                                        To save some storage, a single dependent 
+                                        is kept directly here.
+                                        Otherwise, if there are multiple dependents,
+                                        a collection of dependents is held here.
 
     [author:]
         Claus Gittinger
+
+    [see also:]
+        ValueHolder SelectionInList
+        ( introduction to view programming :html: programming/viewintro.html#MVC )
 "
 ! !
 
@@ -214,22 +225,8 @@
     "Created: 19.4.1996 / 12:19:40 / cg"
 ! !
 
-!Model methodsFor:'drawing'!
-
-displayOn:aGraphicsContext
-    "display myself in aGraphicsContext"
-
-    ^ self subclassResponsibility
-!
-
-displayOn:aGraphicsContext clippingBox:aRectangle
-    "display a part of me in aGraphicsContext"
-
-    ^ self subclassResponsibility
-! !
-
 !Model class methodsFor:'documentation'!
 
 version
-    ^ '$Header: /cvs/stx/stx/libview2/Model.st,v 1.23 1996-04-25 16:43:38 cg Exp $'
+    ^ '$Header: /cvs/stx/stx/libview2/Model.st,v 1.24 1996-05-02 13:28:28 cg Exp $'
 ! !