W3C home > Mailing lists > Public > www-style@w3.org > September 2014

Re: Proposal: Motions along a path in CSS

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 2 Sep 2014 02:08:54 +1000
Message-ID: <CAAWBYDCadY2o0FLpzkznVhWdZp4PFWR_2OkuOiGFZyduqZj-2w@mail.gmail.com>
To: Dirk Schulze <dschulze@adobe.com>
Cc: Sylvain Galineau <galineau@adobe.com>, Shane Stephens <shans@google.com>, "<www-style@w3.org>" <www-style@w3.org>
On Sun, Aug 31, 2014 at 11:18 PM, Dirk Schulze <dschulze@adobe.com> wrote:
> I uploaded a very early draft of motion path here http://dirkschulze.github.io/specs/motion-1/ for every one who is interested.
>
> I did not include Shane’s proposal yet. I would still like to see some examples to understand it better.

Let me explain Shane's proposal a little more.

Motion-on-a-path is just a way of doing some relatively complex
calculations that eventually resolve into, for a given amount of
progress on the path, a translation and a rotation.  So, we can define
this in translate-function terms, like:

motion(<'motion'>)

That is, it's a motion() function, which takes the same grammar as the
'motion' property - a shape, a progress, and a rotation directive.
It's equivalent to a translate()/rotate() pair.

The 'motion' property, then, would just be a property-based variant of
this, which inserts a motion() function into a specific spot at the
beginning of the final transform list.  This has the nice benefits
that it can be independently set and animated and cascaded without
having to worry about any other transforms on the element.

~TJ
Received on Monday, 1 September 2014 16:09:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:46 UTC