Et1 Test Harness: Final Values

Et1 Test Harness: Final Values

This is the Deployment Version (runs from built code). Go to the Developer Version (runs from source code).

Supported Platforms:

IE 5+ on Windows
Known Issue(s):
- Et1 does not provide finals in environments such as IE 5, 6, and 7, since they support neither const nor __defineSetter__ / __defineGetter__. This will probably change with IE 8. See Et1.oContext.Platform.supportsGetAndSet.
Mozilla-based browsers (Firefox 1.0+) on Windows o/s
Known Issue(s):
- None.
Mozilla-based browsers (Firefox 1.0+) on Non Windows o/s
Known Issue(s):
- None.
Safari 3.x
Known Issue(s):
- Only works with basic test. Fortunately, that is adequate for 90% of use-cases in development. The advanced test causes no error, but Safari 3.x does not finalize nested final values.
Safari (2.0.4) on Mac
Known Issue(s):
- Et1 does not provide finals in environments such as Safari 2.x, since they support neither const nor __defineSetter__ / __defineGetter__. See Et1.oContext.Platform.supportsGetAndSet.
Opera 9.5+ on all o/s (does not work < v 9.5; see Et1.oContext.Platform.supportsGetAndSet)
- None.

Verification Targets:

WARNING: Final-values functionality is disabled in the deployment version. Hence, this test should fail.
Et1 uses method calls to define final values at the initialization of any class or interface, which causes Et1 to be too slow for production purposes. Consequently, final values are removed in the deployment version of the code.

Input: Part A-1

Put the parent object name (identifier) or expression (i.e., {}, an empty object-literal) here:

Input: Part A-2

Put the property name (identifier) here:
(For the More Advanced Test, use H_TEST_HASH here).

Input: Part B

Put the final property definition(s) to evaluate here (can be a complex object, a string, etc.):

// Definition of a final value (basic test):
"apple"

/*- 
 *   More Advanced Test (use as an alternate):

// Definition of a final object:
{ 
    sA : "apple", 

    aA : [ "pear", 
           { sB : "blueberry", 
             oB : { 
               sC : "cherry",
               aD : [ 9, 2, { 
                              oC : { sE: "fig" } 
                            } 
                    ]
               } 
           } 
         ], 

    oA : { sD : "date" } 
};

*/

Input: Part B

Put code to try to change the values of the final properties here:

// A test to see if this value can actually be changed:

//     Basic Test:
Et1.oModel.oPage.oConfig.S_TEST = "orange";

//     Use this with the More Advanced Test:
// Et1.oModel.oPage.oConfig.H_TEST_HASH.sA = "orange";

Output: Name-Values