Index: doc/next-tutorial.html =================================================================== diff -u -rb50f8e334d3abf7e807e63be3fc292af69a77d73 -r457985fc87cb99f06989c8c5b4d415500e7d11d1 --- doc/next-tutorial.html (.../next-tutorial.html) (revision b50f8e334d3abf7e807e63be3fc292af69a77d73) +++ doc/next-tutorial.html (.../next-tutorial.html) (revision 457985fc87cb99f06989c8c5b4d415500e7d11d1) @@ -706,7 +706,7 @@ } } -asciidoc.install(3); +asciidoc.install(4); /*]]>*/ @@ -2222,9 +2222,14 @@ incorrect. For all other purposes, the private methods are "invisible" in all situations, e.g. when mixins are used, or within the next-path, etc.
+By using my -local for the invocaton it is possible to call just the +local definition of the method. If we would call the method as usual, +the resoultion order would be the same as usual, starting with +filters, mixins, per-object methods and the full intrinsic class +hierarchy.
…
…
…
The parameter specifications are used in NX for the following purposes. They are used for
The object parameters are not limited to the application defined properties, also NX provides some predefined definitions. Since Person is a subclass of nx::Object also the object parameters of @@ -3140,7 +3151,7 @@ types later.
Since classes are certain kind of objects, classes are parameterized in the same way as objects. A typical parameter for a class definition is the relation of the class to its superclass.In our example, we have @@ -3187,11 +3198,11 @@ parameter definition.
More detailed definition of the object parameter types comes here.
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 @@ -3206,7 +3217,7 @@
Still Missing