- From: Chris Marrin <cmarrin@apple.com>
- Date: Mon, 23 Jul 2012 09:22:19 -0700
- To: "L. David Baron" <dbaron@dbaron.org>
- Cc: Dirk Schulze <dschulze@adobe.com>, "www-style@w3.org" <www-style@w3.org>
Received on Monday, 23 July 2012 16:22:59 UTC
On Jul 19, 2012, at 5:51 PM, L. David Baron <dbaron@dbaron.org> wrote: > On Thursday 2012-07-19 16:54 -0700, Dirk Schulze wrote: >> Do I understand your point correctly, that you just want the >> affected transformation functions to get interpolated as matrices? > > Yes, rather than forcing the entire list to be interpolated as a > single matrix. You're complicating the rules by doing this. If I have: rotate(...) scale(...) translate(...) scale(...) rotate(...) translate(...) Do you do two separate matrix animations? Taking that to its logical conclusion, you could end up doing a dozen expensive matrix animations for a long list of unmatched primitives. Or do you combine unmatching primitives next to each other? That might be a better approach, but it might get confusing for long primitive lists. We also talked about adding an identity() primitive to make it easier to match up primitives. Identity() would match a primitive of any type. Was that ever done? ----- ~Chris Marrin cmarrin@apple.com
Received on Monday, 23 July 2012 16:22:59 UTC