Deutsch   English   Fran├žais   Italiano  
<d8ff311f-3141-45c9-9c5f-bca1cf226efe@googlegroups.com>

View for Bookmarking (what is this?)
Look up another Usenet article

X-Received: by 10.224.205.138 with SMTP id fq10mr1073089qab.1.1371110904446;
        Thu, 13 Jun 2013 01:08:24 -0700 (PDT)
X-Received: by 10.49.35.195 with SMTP id k3mr364501qej.2.1371110904382; Thu,
 13 Jun 2013 01:08:24 -0700 (PDT)
Path: ...!usenet.blueworldhosting.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!ch1no5618346qab.0!news-out.google.com!y6ni1854qax.0!nntp.google.com!ch1no5618341qab.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.tcl
Date: Thu, 13 Jun 2013 01:08:24 -0700 (PDT)
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=91.113.33.38; posting-account=hc9W-AkAAAA3t8I5aI3sdC5I5eHMjDWA
NNTP-Posting-Host: 91.113.33.38
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d8ff311f-3141-45c9-9c5f-bca1cf226efe@googlegroups.com>
Subject: Announcement: Next Scripting Framework 2.0b5 available
From: gustafn <neumann@wu-wien.ac.at>
Injection-Date: Thu, 13 Jun 2013 08:08:24 +0000
Content-Type: text/plain; charset=ISO-8859-1
X-Received-Bytes: 11017

Dear Community,

This is an announcement of the availability of the 
Next Scripting Framework 2.0b5, which contains fully 
scripted versions of XOTcl and NX (see http://next-scripting.org).

Since the last release of the the Next Scripting Framework
(NSF 2.0b3), we have received various feedback from early adopters. 
Many thanks for the helpful and the constructive comments!

This feedback triggered an internal discussion and led to revising
some earlier design decisions and naming conventions, especially
in NX. The new naming conventions improve the orthogonality and
the clarity of NX programs.

Since the release of 2.0b3, there have been more than 250 commits to
our code repository. The implementation is very stable and has been
used for more than two years in production of our large-scale,
multi-threaded web environment inside NaviServer. Most of the changes
happened in NX and, therefore, on the NSF scripting level, without the
need to modify the NSF C layer. The implementation of XOTcl 2 has
changed very little. The Next Scripting Framework was tested with Tcl
8.5.14 and Tcl 8.6.0 on Linux, Mac OS X, and in windows environments
(MinGW, VC11).

This beta-release is supposed to be the last release before
the final 2.0 is out, which should be soon.

Below are the most notable differences in 2.0b5 as compared to
2.0b3:

a) NX 2.0b3 used the following conventions to define methods for
   instances, object-specific methods and class-object specific
   methods:

     /cls/ method foo {args} {...}
     /obj/ method bar {args} {...}
     /cls/ class method baz {args} {...}

   Introspection was possible via (in the same order):

     /cls/ info methods
     /obj/ info methods
     /cls/ class info methods

   The problem with this convention is that e.g. "info methods"
   operates on different method records, depending on whether it is
   called on a class or on an object. This breaks a basic inheritance
   contract with the programmer: As nx::Class is a specialization of
   the most general class nx::Object, the same introspection operation
   (e.g., "info methods") should return e.g. object-specific methods
   for both class objects and ordinary, non-class objects.

   Therefore, we adopted the following more orthogonal
   conventions to define methods for instances and
   for object-specific methods

     /cls/ method foo {args} {...}
     /obj/ object method bar {args} {...}

   Introspection:

     /cls/ info methods
     /obj/ info object methods

   Note that we can now use the same mechanism to define
   or query object-specific methods on objects and classes.
   The same applies for aliases, forwards, mixins, and filters.

   The new convention imposes a little typing burden for the code
   writer, but reduces the potential ambiguity for the code reader,
   who is trying to understand what exactly "$x method FOO {args}
   {...}" means.

   For convenience, we provide two packages "nx::plain-object-method"
   and "nx::class-method" to switch to the old conventions. A verbose
   tracing mode can report usages to ease migration.


b) Parametrization:

   NX 2.0b3 followed the XOTcl conventions of registering by default
   same-named getter/setter methods for configuration parameters used
   in object creation. These getter/setter methods bloat the method
   interface and risk shadowing inherited methods, leading to
   unexpected behaviors for beginners.

   NX 2.0b5 adopts a Tk/itcl/... idiom by offering a cget/configure
   interface to objects as generic getters/setters. To obtain
   parameter-specific getters/setters (i.e., the old behavior), the
   flag "-accessor public|protected|private" can be set when defining
   properties and variables.

c) Further clean-ups of the introspection interface ("info").

   In order to streamline the interface further, we followed the idea
   to use "... info /plural word/" to obtain a set of handles, and
   then to make a separate call to retrieve the details. Therefore, we
   now provide ...

     /cls/ info methods
     /obj/ info object methods

     /cls/ info variables
     /obj/ info object variables

     /cls/ info slots
     /obj/ info object slots

     /cls/ info method parameters /methodName/
     /obj/ info object method parameters /methodName/

     /cls/ info configure parameters
     /obj/ info lookup configure parameters

   ... to return a list of handles. The result list can be filtered in
   each case by specifying a match pattern. Each result handle can
   then be used in a separate call to obtain details:

     /obj/ info method definition /methodHandle/
     /obj/ info variable definition /varHandle/
     /obj/ info parameter name /paramHandle/

   These are just a few examples.

   In NX 2.0b3, we had e.g. "... info parameter definitions ..."
   leaving a beginner in the dark about the parameters actually
   meant. Also, the introspection interface made mixed use of plural
   and singular wordings for different purposes (e.g., retrieving
   collections and/or detailed information on one item).

Below is a more detailed summary of the changes.

The Next Scripting Framework 2.0b5 (containing NX and XOTcl 2.0b5) can
be obtained from http://next-scripting.org/

Best regards
- Gustaf Neumann
- Stefan Sobernig

===============================================

Announcing NSF 2.0b5
*************************

Major changes relative to NSF 2.0b3 are (in addition of
the items (a), (b), and (c) above) are:

   * Additional Features:

     - Serializer:
       * Added flag -objmap to Serializer method deepSerialize
         to make serializer to provide mapping only for
         object names. This makes the serializer
         usable for object/class copying (-map is too coarse)
       * Made "ignore" method public
       * Due to the split between serializer and object
         system serializer, the "ignore" settings were lost

      - Allow explicit unsetting of -per-object flag in 0-argument
    "-flag=value" notation (all built-in commands accepting this flag)

     - Better compatibility with XOTcl 1.*:

     - Added "/obj/ info name" (as alternative to
       "namespace tail [self]")

     - Test-suite: added summary with statistics

     - Traits: added property/variable inheritance

     - MongoDB
    - Added "nx::mongo::db drop collection /name/"
    - Returning status from "nx::mongo::db remove" as success (0 or 1)
    - Adjust to object interface
    - Reduce verbosity
    - Add error messages for slot lookup failures

    Updated MongoDB interface
    - Upgraded to c-driver 0.7.1
========== REMAINDER OF ARTICLE TRUNCATED ==========