Re: transitions vs. animations

Also sprach Chris Marrin:

 > >   http://people.opera.com/howcome/2010/ta/index.html
 > 
 > Let me split this into two issues:

I agree that the proposal contains ideas that can be discussed
separately.

 > 1) Unified syntax for animation and transition
 > 
 > Here you are incorporating the animation-name property into the
 > single 'effect' shorthand. This gets rid of a few animation
 > properties, but at the expense of readability and increased
 > complexity.

I think the unified model is simpler, and more readable. Fewer
properties, fewer terms that can be confused.

I don't expect you to like any change proposals, though :)

 > What does it mean if I specify direction or iteration-count for a
 > transition?

I expect most humans to use the shorthand syntax where this is not an
issue. Also, it's not an issue if we use the functonal notation (as
suggested towards the end). The worst case is that the values have to
be ignored.

 > 2) Additional ways of triggering an animation
 > 
 > This is a good feature to discuss. I just don't think "on-exit" and
 > the related concepts are a clear way to express it.

How would you like to fill in the empty boxes?:

   http://people.opera.com/howcome/2010/ta/index.html

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome

Received on Thursday, 8 April 2010 00:05:05 UTC