I was thinking of trying to rewrite the kernel stuff as JS classes as we can
in an opportunistic manner; as we
merge sw8 and swf9 stuff that touches the kernel,
like if we merge the LzModeManager code together, it ought to turn into a
class (I already did that in the swf9
LzModeManager.js file).
On Tue, Mar 25, 2008 at 8:42 AM, P T Withington <[EMAIL PROTECTED]> wrote:
> Well there are two options:
>
> 1) AS3 does support prototype still, so you could put it on the
> LzSprite prototype in all runtimes
>
> 2) It does seem that it is more of a class var though, so you could
> also re-write the 'structure type' version to store it on the type
> rather than the prototype.
>
> I still regret I was not able to convince Max to write the swf & dhmtl
> kernels in lzs. I understand the principle, but so far it has only
> been a principle -- it hasn't bought us anything else.
>
> On 2008-03-24, at 23:42 EDT, Henry Minsky wrote:
> > In LzView, there is this declaration
> >
> > var capabilities = LzSprite.prototype.capabilities;
> >
> > In swf9, I have "capabilities' declared as a static class var
> >
> > public static var capabilities:* = { ...}
> >
> > So I would reference it as LzSprite.capabilities.
> >
> > In swf and dhtml kernels, LzSprite is defined as a javascript object
> > with
> > properties stuck on it's
> > prototype:
> > LzSprite.prototype.capabilities = {....}
> >
> > How should I reconcile these two different mechanism to get this
> > value? I am
> > currently doing this
> > in LzView:
> > if ($swf9) {
> > var capabilities = LzSprite.capabilities;
> > } else
> > var capabilities = LzSprite.prototype.capabilities;
> > }
> >
> >
> >
> >
> > So what is the best way to
> >
> > --
> > Henry Minsky
> > Software Architect
> > [EMAIL PROTECTED]
>
>
--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
