This can be a problem when the class instances are not - reloaded and when they should survife the redefintion with the + reloaded and when they should survife the redefinition with the same class relationships. Therefore we define a meta class RecreationClass, which can be used to parameterize the behavior on redefinitions. Alternatively, Classes or objects could provide their own recreate methods.
-Per default, this meta-class handles only the class redefintion +
Per default, this meta-class handles only the class redefinition case and does only a reconfigure on the class object (in order to get e.g. ad_doc updated).
The following parameters are defined: Index: openacs-4/packages/xotcl-core/tcl/generic-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/generic-procs.tcl,v diff -u -r1.97.2.9 -r1.97.2.10 --- openacs-4/packages/xotcl-core/tcl/generic-procs.tcl 1 Oct 2016 11:10:46 -0000 1.97.2.9 +++ openacs-4/packages/xotcl-core/tcl/generic-procs.tcl 22 Apr 2017 16:59:39 -0000 1.97.2.10 @@ -196,7 +196,7 @@ The method generate is used to actually generate the form template from the specifications and to set up page_title and context when appropriate. - @param template is the name of the tcl variable to contain the filled in template + @param template is the name of the Tcl variable to contain the filled in template @param export list of attribue value pairs to be exported to the form (nested list) } { # set form name for adp file Index: openacs-4/packages/xotcl-core/tcl/html-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/html-procs.tcl,v diff -u -r1.3.2.1 -r1.3.2.2 --- openacs-4/packages/xotcl-core/tcl/html-procs.tcl 21 Apr 2017 14:00:24 -0000 1.3.2.1 +++ openacs-4/packages/xotcl-core/tcl/html-procs.tcl 22 Apr 2017 16:59:39 -0000 1.3.2.2 @@ -46,7 +46,7 @@ # # -option name of HTML attribute # value attribute value - # script tcl script to run in command's context. + # script Tcl script to run in command's context. # # Example: table -border 1 {...} # Index: openacs-4/packages/xowf/tcl/xowf-form-field-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowf/tcl/xowf-form-field-procs.tcl,v diff -u -r1.2.2.4 -r1.2.2.5 --- openacs-4/packages/xowf/tcl/xowf-form-field-procs.tcl 6 Mar 2017 00:12:32 -0000 1.2.2.4 +++ openacs-4/packages/xowf/tcl/xowf-form-field-procs.tcl 22 Apr 2017 16:59:39 -0000 1.2.2.5 @@ -91,7 +91,7 @@ # -# these definitons are only here for the time being +# these definitions are only here for the time being # namespace eval ::xo::role { Class create Role Index: openacs-4/packages/xowf/tcl/xowf-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowf/tcl/xowf-procs.tcl,v diff -u -r1.3.2.14 -r1.3.2.15 --- openacs-4/packages/xowf/tcl/xowf-procs.tcl 21 Apr 2017 15:11:28 -0000 1.3.2.14 +++ openacs-4/packages/xowf/tcl/xowf-procs.tcl 22 Apr 2017 16:59:39 -0000 1.3.2.15 @@ -1716,7 +1716,7 @@ } WorkflowPage ad_instproc schedule_job {-time:required -party_id cmd} { - Schedule the specified tcl command for the the current package + Schedule the specified Tcl command for the the current package instance at the given time. } { my instvar package_id Index: openacs-4/packages/xowiki/tcl/menu-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowiki/tcl/menu-procs.tcl,v diff -u -r1.8.2.9 -r1.8.2.10 --- openacs-4/packages/xowiki/tcl/menu-procs.tcl 21 Apr 2017 13:51:54 -0000 1.8.2.9 +++ openacs-4/packages/xowiki/tcl/menu-procs.tcl 22 Apr 2017 16:59:39 -0000 1.8.2.10 @@ -120,7 +120,7 @@ # 3) All menu entry names should be named after the menu name # # Notice: the current implementation uses interally dicts. Since the - # code should as well work with tcl 8.4 instances, we provide a + # code should as well work with Tcl 8.4 instances, we provide a # compatibility layer. Maybe it would be better to base the code on # an ordered composite. Ideally, the interface should stay mostly # compatible. Index: openacs-4/packages/xowiki/tcl/xowiki-www-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowiki/tcl/xowiki-www-procs.tcl,v diff -u -r1.327.2.30 -r1.327.2.31 --- openacs-4/packages/xowiki/tcl/xowiki-www-procs.tcl 22 Feb 2017 10:03:30 -0000 1.327.2.30 +++ openacs-4/packages/xowiki/tcl/xowiki-www-procs.tcl 22 Apr 2017 16:59:39 -0000 1.327.2.31 @@ -1943,7 +1943,7 @@ } if {[$field nodeName] ne "input"} continue # - # We handle now only INPUT types, but we have to differntiate + # We handle now only INPUT types, but we have to differentiate # between different kinds of inputs. # set type [expr {[$field hasAttribute type] ? [$field getAttribute type] : "text"}] Index: openacs-4/packages/xowiki/tcl/upgrade/upgrade.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowiki/tcl/upgrade/upgrade.tcl,v diff -u -r1.11.2.7 -r1.11.2.8 --- openacs-4/packages/xowiki/tcl/upgrade/upgrade.tcl 21 Apr 2017 13:51:54 -0000 1.11.2.7 +++ openacs-4/packages/xowiki/tcl/upgrade/upgrade.tcl 22 Apr 2017 16:59:39 -0000 1.11.2.8 @@ -9,7 +9,7 @@ namespace eval ::xowiki { # - # For the time being, we keep the __upgrade proc a single tcl + # For the time being, we keep the __upgrade proc a single Tcl # function. We could split it into separate files like the sql # upgrade scripts, but on one hand side, the upgrade snippets are # often similar, so it is convenient to reuse the logic from there,