Index: doc/next-migration.html =================================================================== diff -u -rd725e5e4cfc9f89d78e781e6ce27900e199ba8c5 -rd303212e06bfd89c57038a26ba54f9f86e941601 --- doc/next-migration.html (.../next-migration.html) (revision d725e5e4cfc9f89d78e781e6ce27900e199ba8c5) +++ doc/next-migration.html (.../next-migration.html) (revision d303212e06bfd89c57038a26ba54f9f86e941601) @@ -736,8 +736,8 @@

Migration Guide for the Next Scripting Language

Gustaf Neumann
<neumann@wu-wien.ac.at>
-version 2.0.0, -November 2014 +version 2.1.0, +December 2016
Table of Contents
@@ -858,7 +858,7 @@

  • -One can define in NX hierachical method names (similar to +One can define in NX hierarchical method names (similar to commands and subcommands, called method ensembles) in a convenient way to provide extensible, hierarchical naming of methods. @@ -1003,7 +1003,7 @@

    Much Smaller Interface: The Next Scripting Language has a much smaller interface (i.e. provides less predefined methods) than - XOTcl (see Table 1), although the expressability was increased in + XOTcl (see Table 1), although the expressiveness was increased in NX.

    • @@ -1163,7 +1163,7 @@

    In general, the Next Scripting Framework supports multiple object systems concurrently. Effectively, every object system has different base classes for creating objects and classes. Therefore, these object -systems can have different different interfaces and names of built-in +systems can have different interfaces and names of built-in methods. Currently, the Next Scripting Framework is packaged with three object systems:

    In NX forwarders are called forward. NX does not provide an public available method to define variable accessors like parametercmd in -XOTcl, but use interanlly the Next Scripting Framework primitive +XOTcl, but use internally the Next Scripting Framework primitive nsf::method::setter when appropriate.

    +operations in constructors, this is as well possible in NX.

    NX uses the same mechanism to define class variables or object variables.

    @@ -2612,8 +2612,8 @@

    In the next step, we define configurable instance variables which we call properties in NX.

    XOTcl uses the method parameter is a shortcut for creating multiple -configurable variables with automically created accessors (methods for -reading and writing of the variables). In NX, the prefered way to +configurable variables with automatically created accessors (methods for +reading and writing of the variables). In NX, the preferred way to create configurable variables is to use the method property. The method property in NX is similar to variable, but makes the variables configurable, which means that

    @@ -2953,7 +2953,7 @@ to be passed to the constructor of the object.

    NX allows to define optional and required configure parameters (as well as method parameters). Therefore, configure parameters can be used -as the single mechanism to parameterize objects. It is in NX not +as the single mechanism to parametrize objects. It is in NX not necessary (and per default not possible) to pass arguments to the constructor.

    @@ -3192,7 +3192,7 @@

    Since the slots are objects, the slot objects can be configured and -parameterized like every other object in NX. Slot objects can be +parametrized like every other object in NX. Slot objects can be provided with a scripted initialization as well. We show first the definition of properties simliar to the functionality provided as well by XOTcl and show afterwards how to use value constraints, optional @@ -3571,7 +3571,7 @@ namely class- and object-level mixins and class- and object-level filters. The primary difference in NX is the naming, since NX abandons the prefix "inst" from the names of instance specific method, but uses -the the modifier objec" for object specific methods.

    +the modifier object" for object specific methods.

    Therefore, in NX, if a mixin is registered on a class-level, it is applicable for the instances (a per-class mixin), and if and object mixin is registered, it is a per-object mixin. In both cases, the @@ -3795,7 +3795,7 @@

    In NX, one can use e.g. always info method with a subcommand and the framework tries to hide the differences as far as possible. So, one can for example obtain with info method parameter the parameters of -scripted and C-implemented methods the same way, one one can get the +scripted and C-implemented methods the same way, one can get the definition of all methods via info method definition and one can get an manual-like interface description via info method syntax. In addition, NX provides means to query the type of @@ -5473,7 +5473,7 @@ .nx-placeholder {color: #AF663F; font-weight: normal; font-style: italic;} .nx-variable {color: #AF663F; font-weight: normal; font-style: normal;} -

    cd # Check if object is an NX class
+
    # Check if object is an NX class
 /obj/ has type ::nx::Class
 
 # Check if object is a class in one of the
@@ -6432,7 +6432,7 @@
 
    
 
    3.4. Obsolete Commands
    
 
    Parameter-classes were rarely used and have been replaced by the more
-general object parameterization. Therefore, cl info parameterclass has
+general object parametrization. Therefore, cl info parameterclass has
 been removed.
    
 
    
 
    
@@ -6465,8 +6465,8 @@