- From: Shane Stephens <shans@google.com>
- Date: Thu, 31 Oct 2013 07:09:49 +1100
- To: MLC 大関哲治 <ohzeki-tetsuharu@mitsue.co.jp>
- Cc: "public-fx@w3.org" <public-fx@w3.org>
Hi Ohzeki-san,
The reason for this is that CustomEffect objects are provided by the
users of Web Animations, whereas the other Effect objects are part of
the model.
We want users to be able to build their own CustomEffect classes, so
we provide a specification of the minimal requirements that these
objects need to have. This lets users create objects with their own
constructors, hierarchies, behaviours, etc.
Sincerely,
-Shane Stephens
On Wed, Oct 30, 2013 at 5:57 PM, MLC 大関哲治 <ohzeki-tetsuharu@mitsue.co.jp> wrote:
> Hi public-fx,
>
> I have some questions about Web Animations CustomEffect.
>
> At the current web animations working/editors draft, I saw that CustomEffect interfaces doesn't have constructor like other AnimationEffect. I think this design is not uniform with other effects.
>
> Why do we have no CustomEffect constructor? If we don't have any reasons that have no constructors of CustomEffects, I propose that CustomEffects should have it.
>
> Best regards.
>
> --
> Tetsuharu OHZEKI
>
>
Received on Wednesday, 30 October 2013 20:10:23 UTC