commit-gnue
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnue/common/doc TriggerSpecifications.txt


From: James Thompson
Subject: gnue/common/doc TriggerSpecifications.txt
Date: Wed, 23 Jan 2002 20:52:43 -0500

CVSROOT:        /cvsroot/gnue
Module name:    gnue
Changes by:     James Thompson <address@hidden> 02/01/23 20:52:43

Modified files:
        common/doc     : TriggerSpecifications.txt 

Log message:
        Syncing notes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gnue/gnue/common/doc/TriggerSpecifications.txt.diff?tr1=1.10&tr2=1.11&r1=text&r2=text

Patches:
Index: gnue/common/doc/TriggerSpecifications.txt
diff -c gnue/common/doc/TriggerSpecifications.txt:1.10 
gnue/common/doc/TriggerSpecifications.txt:1.11
*** gnue/common/doc/TriggerSpecifications.txt:1.10      Wed Jan 23 20:30:46 2002
--- gnue/common/doc/TriggerSpecifications.txt   Wed Jan 23 20:52:43 2002
***************
*** 163,172 ****
    end
  
  
- 
- 
- 
- 
  ---------------------------
  Jason's Scratchpad: 
  ---------------------------
--- 163,168 ----
***************
*** 274,301 ****
  
  Extend GObj to add trigger support at this level
  
  * Any object from the top level object is referenced by it's name
  
! * 2 arrays exist triggerAttributes and triggerFunctions which will
!   be populated by the GObj based objects author.  They will contain
!   references to functions. This may be conbinable
  
  * Any object can tag itself as a global object which will make it available
!   to all other objects via it's name
  
  * Any object can reference itself via a self. reference or it's own name
  
! * A hook might be made available for internal properties manipulation
  
! * Do we need "transparent" objects that can opt out of the trigger namespace
!   yet allow their children to be in
  
  
  At init time the GObj tree is parsed.  The following objects are created and 
placed
! into a global trigger namespace.  
  
  GTriggerObject
    * Created for each GObj that requires inclusion in the trigger namespace
    * Contains attributes that link to GTriggerFunction and GTriggerAttribute 
objects
    * Contains the following extra attributes: 
    *   self
--- 270,311 ----
  
  Extend GObj to add trigger support at this level
  
+ 
+ BEGIN: Custom namespace construction system
+ 
  * Any object from the top level object is referenced by it's name
  
! * a dictionary exists ()_triggerNamespace and will be populated by the GObj 
based 
!   object's author.  It will contain references to functions and attributes. 
! 
!   _triggerNamespace = {
!                         'exposedName', internal var or function
!                       }
!   This will be used to construct the object tree described below
  
  * Any object can tag itself as a global object which will make it available
!   via it's name in the global namespace
  
  * Any object can reference itself via a self. reference or it's own name
  
! * A hook will be made available for internal properties manipulation
!   _triggerProperties = {
!                          'exposedPropertyName', { 'set', function that will 
set the value
!                                                   'get', function that will 
get the value
!                                                 } 
!                        }
  
! * transparent objects can opt out of the trigger namespace yet allow their 
!   children to be in
  
  
  At init time the GObj tree is parsed.  The following objects are created and 
placed
! into a global trigger namespace.  Any objects found in the tree that request 
global
! namespace assignment also get put into the global namespace.  
  
  GTriggerObject
    * Created for each GObj that requires inclusion in the trigger namespace
+   * Contains attributes that link to each of it's children's GTriggerObjects 
by their name
    * Contains attributes that link to GTriggerFunction and GTriggerAttribute 
objects
    * Contains the following extra attributes: 
    *   self
***************
*** 316,318 ****
--- 326,338 ----
  fired against it.
  
  
+ GObj extensions
+   _triggerGlobal : Always put this object in the global trigger namespace by 
it's name
+ 
+   _triggerTransparent : Do not add this object to the trigger namespace 
however bump
+                         it's children up to look as if they are assigned to 
this object's
+                         parent in the trigger namespace.
+ 
+ 
+ 
+ END: Custom namespace construction system



reply via email to

[Prev in Thread] Current Thread [Next in Thread]