The goal of this group is to create a specification that defines methods to write rates of change into a webpage. I am aware that there exist a couple of methods currently defined by the W3C that define similar functionality, but they implement interim states between static values instead of inherent change, as well as other problems. I think that a better specification can be written to define movement and change within the markup and stylesheets.
\nMy goals for the specification are:
\n1.\tTo define as little new behavior as possible. Any advice or specifications resulting from this group will conform as closely as possible to CSS’s syntax.
\n2.\tTo create as intuitive a specification as possible. Any method defined by the group should be easily understood by a developer new to CSS. It should not be overly complicated.
\n3.\tTo require minimal scripting. While code can be used to create animation and change, minimal scripting generally results in shorter, simpler and more readable markup.
\n4.\tTo allow granular control. Rates should be able to be controlled and changed when the author requires.
\nThese are my ideas, but I am very open to any differing opinions. The group should be as open to ideas as possible; please tell me if you have any advice or disagreements with regard to this post.
\nAs well, part of the group’s goals are to complete a specification, and it will therefore require people to write one. Does anyone wish to volunteer as a specification author?
\nThanks for your interest in the CSS Rates and Velocities Community Group, and I encourage your participation and discussion within it.<\/p>\n","protected":false},"excerpt":{"rendered":"
The goal of this group is to create a specification that defines methods to write rates of change into a webpage. I am aware that there exist a couple of methods currently defined by the W3C that define similar functionality, … Continue reading