Index: TODO =================================================================== diff -u -r4271f1017962a2fc3613d6be3f31f01ef2f63d82 -r57570354bfebc1bc24f1ba3d7976c44b2c2bd3e9 --- TODO (.../TODO) (revision 4271f1017962a2fc3613d6be3f31f01ef2f63d82) +++ TODO (.../TODO) (revision 57570354bfebc1bc24f1ba3d7976c44b2c2bd3e9) @@ -2328,6 +2328,8 @@ - nsf::relation: fixed error message when receiving and invalid class for relation type "class" +- updated documentation + TODO: - document value added replacements of Tcl functions @@ -2339,12 +2341,10 @@ - slotmachinerie 2 - naming "incremental", "reconfigure" - - check: - ? {o1 class add M} {class: expected a class but got "::o1"} - - should we deactivate add/delete for non-multivalued cases? - - allow noarg+default/initcmd ? - - default/initcmd/subsdefault: can we simplify these? - or add messages for conflicting usages. + - should we deactivate add/delete for non-multivalued cases? + - allow noarg+default/initcmd ? + - default/initcmd/subsdefault: can we simplify these? + or add messages for conflicting usages. - doc: NextScriptingLanguage/index.html: @@ -2373,7 +2373,6 @@ * __unknown unknown is a hook for Object but a method for Class - - do we need contains in nx? - are the oneline hook definitions like Class protected class-object method __unknown {name} {} Index: doc/next-tutorial.html =================================================================== diff -u -re87fe21651b656a0aebe214c6d7ca1866d5b2289 -r57570354bfebc1bc24f1ba3d7976c44b2c2bd3e9 --- doc/next-tutorial.html (.../next-tutorial.html) (revision e87fe21651b656a0aebe214c6d7ca1866d5b2289) +++ doc/next-tutorial.html (.../next-tutorial.html) (revision 57570354bfebc1bc24f1ba3d7976c44b2c2bd3e9) @@ -818,7 +818,7 @@

2.2. Define an Object named stack

-

The definition of the stack in Listing 3 +

The definition of the stack in Listing 2 is following the traditional object oriented approach, found in practically every object oriented programming language: Define a class with some methods, create instances from this class, and use the @@ -2069,12 +2069,13 @@ instance variables of objects are initialized and how these objects could be parameterized.

-

Syntactically, object and method parameters are the same, although -there are certain differences (e.g. some parameter options are only -applicable for objects parameters, the list of object parameters is -computed dynamically, object parameters are often used in combination -with special setter methods, etc.). Consider the following example, -where we define two application classes with a few attributes.

+

Syntactically, object parameters and method parameters are the same, +although there are certain differences (e.g. some parameter options +are only applicable for objects parameters, the list of object +parameters is computed dynamically from the class structures, object +parameters are often used in combination with special setter methods, +etc.). Consider the following example, where we define the two +application classes Person and Student with a few attributes.

Listing 24: Object Parameters

+
  1
+  2
+  3
+  4
+
Object parameter for Class Student:
+   -mixin:alias -filter:alias ...
+   {-superclass:alias ::nx::Object} ...
+   -attributes:alias _:initcmd,optional
+ +
+

3.2.3. Additional Parameter Types for Object Parameters

+

More detailed definition of the object parameter types comes here.

+
+
+

3.2.4. Slot Classes and Slot Objects

+

In one of the previous sections, we defined scripted (application +defined) checker methods on a class named nx::Slot. In general NX +offers the possibility to define value checkers not only for all +usages of parameters but as well differently for method parameters or +object parameters

slots.png
-
Figure 27. Slot Classes and Objects
+
Figure 28. Slot Classes and Objects

-

3.2.2. Special Object Parameters

-
-
-

3.2.3. Attribute Slots

+

3.2.5. Attribute Slots

Still Missing