<html>
<body>
Hi Henry,<br><br>
There is code in the data classes that specify setters. For example, this
code is in LzDataText.lzs:<br><br>
setters.data = "setData";<br><br>
<br>
Can this be done in a static initializer? The original traits use this
method to install setters. The code compiles in swf9 but I don't know if
it works. For example, in the class LzMiniNode_DataNode_DOM (my manually
instantiated class):<br><br>
static function initialize (prototype) {<br>
// There will be no setters property in
the trait prototype,<br>
// (and you don't want one there! as it
would shadow the one<br>
// from LzNode) but it will be there after
LzNode.initialize<br>
// runs<br>
if (prototype.hasOwnProperty('setters'))
{<br>
// since you can't assign
directly to these slots...<br>
// until LzNode.initialize has
run<br>
prototype.setters.attributes =
"setAttrs";<br>
prototype.setters.childNodes =
"setChildNodes";<br>
prototype.setters.nodeName =
"setNodeName";<br>
// Shouldn't be directly
settable<br>
prototype.setters.ownerDocument = "setOwnerDocument";<br>
}<br>
}<br><br>
<br><br>
<blockquote type=cite class=cite cite="">Yes, look at LaszloView.js or
LzText.js for examples what I've been doing. I declare static class vars
like this, which make copies of the superclass's setters vars<br>
<br>
static var getters = new
LzInheritedHash(LFCNode.getters);<br>
static var defaultattrs = new
LzInheritedHash(LFCNode.defaultattrs);<br>
static var options = new
LzInheritedHash(LFCNode.options);<br>
static var setters = new
LzInheritedHash(LFCNode.setters);<br>
static var __LZdelayedSetters:* = new
LzInheritedHash(LFCNode.__LZdelayedSetters);<br>
static var earlySetters:* = new
LzInheritedHash(LFCNode.earlySetters);<br>
<br>
And the base constructor in LFCNode (which is the 'static' version of
LzNode, see core/LzNode.js) automatically copies these class vars to the
corresponding instance vars when a node is constructed.<br>
<br>
<br>
Note, there's an issue at runtime that comes up if you have code which
tries to set arbitrary properties on a class which have not been declared
at compile time. To allow this, the class has to be declared
'dynamic'.<br>
Eventually we're going to make <attribute> declarations cause
compile-time declarations of instance vars, but we don't do that yet so
I've been doing the following thing:<br>
<br>
I have an idiom I am using in LzNode and LzView whereby I have an
"internal" class, LFCNode, or LFCView, which is not declared
'dynamic', and then I have a kind of 'wrapper' class which I declare as
'dynamic', (e.g., LzNode, LzView). This is to get the (hoped for) benefit
of the as3 compiler making more efficient code for accessors to
methods and instance vars of these superclasses because they are
not declared dynamic.<br>
<br>
For the data classes, I think they can all just be left as they are, and
not declare them dynamic, and see if we can get them to compile.<br>
For now if something subclasses LzNode, just leave it doing that.<br>
Eventually we may want to make that subclass LFCNode instead. At runtime,
if we discover that there are classes where code which is adding
properties dynamically at runtime, we can see about making a 'dynamic'
subclass for those classes, or just declare them dynamic, or
something.<br>
<br>
<br>
<br>
<br>
On Fri, Feb 1, 2008 at 10:27 AM, Philip Romanik
<<a href="mailto:promanik@laszlosystems.com">
promanik@laszlosystems.com</a>> wrote:<br>
> Hi Henry,<br>
> <br>
> What is the "new" way to handle setters in swf9? The
solution you're <br>
> using in LaszloView looks like,<br>
> <br>
> static var setters = new
LzInheritedHash(LFCNode.setters); ...<br>
> LFCView.setters.clip = -1;<br>
> <br>
> <br>
> Should I use this same approach with the files I'm
porting?<br>
> <br>
> Thanks!<br>
> <br>
> Phil<br>
> <br>
> <br>
<br>
<br>
<br>
-- <br>
Henry Minsky<br>
Software Architect<br>
<a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</a>
</blockquote></body>
</html>