Re: Summary of discussion about FX work items

Hi Vincent, thanks for restarting this discussion on the list.

Vincent Hardy:
> Animation.
> 
> The WG thinks that we should:
> 
> a. Coordinate with the CSS WG to make sure that both transitions and
> animations can be made to work with SVG properties and attributes.
> 
> b. Work with the CSS in the FX task force on CSS Animations, in particular
> on issues such as keyFrames to try and have a consistent model.
> 
> c. Discuss the need for more timing and synchronization support as well as
> an animation API and decide if the FX task force is the right place to
> have that work.

I would like to have concrete preferences to take back to the CSS WG
about what specifications should exist and where.  Just to clarify, it
seems the above says:

  * CSS Transitions remains in the CSS WG.  We will provide input on it
    to ensure that transitions can traget SVG properties and attributes.

  * CSS Animations moves to the FX TF.

  * We might have a specification for defining timing, synchronisation
    and script APIs in the future, but it is not yet decided where that
    specification would live.  This specification would be referenced by
    SVG 2.0 and whatever other CSS-syntax animation specifications
    exist.

Is that accurate?

I’m unsure that having Transitions remain a CSS-only specification while
having Animations be a joint FX specification is the best way forward.
It seems to me that either both or neither should be joint
specifications.  Transitions defines things (timing functions, how to
interpolate particular data types, which properties can be transitioned)
that impact upon transitions being applicable to SVG content just as
much as Animations does.  Even if we decide that SVG attributes cannot
be transitioned, the definitions of timing functions etc. are reused in
the CSS Animations spec.

-- 
Cameron McCormack ≝ http://mcc.id.au/

Received on Thursday, 16 June 2011 23:06:42 UTC