[Laszlo-user] API change proposal for states and apply

[Vagelis Papadogiannakis]

Its been a while since I last wrote to this list, but I read it allways!

Congratulations to PT, this idea is very nice and... "logical"

I think he is absolutely right and the change has to be "applied" ;)

Keep up the good work!

Vagelis




On Thu, May 15, 2008 at 2:23 AM, P T Withington <ptw at pobox.com> wrote:
> We need to clean up the API for states.  Right now states have both an
> attribute _and_ a method named `apply`.  This just makes no sense.  It is
> implemented by a horrendous kludge that we will not be able to carry forward
> into Javascript 2 runtimes.  Here's my proposal:
>
> 1) Deprecate `apply` the attribute.  Replace it with `applied`, which is a
> read/write attribute whose value reflects whether or not the state is
> currently applied.  (There is currently a property `isapplied` that is
> read-only that tells the state of a state, but this name is inconsistent
> with our name conventions.  As a part of this proposal, deprecate
> `isapplied` and replace it with `applied`.
>
> The `apply` method (and it's counterpart `remove`) remain, but the preferred
> method for controlling a state is to constrain the `applied` property.
>
> We can add to the 4.x upgrade script a template that looks for `apply` in
> the open tag of a state and replaces it with `applied`.
>
> Comments?
>