- From: Paul LeBeau <paul.lebeau@gmail.com>
- Date: Thu, 4 Jun 2015 23:10:51 +1200
- To: Brian Birtles <bbirtles@mozilla.com>
- Cc: www-svg <www-svg@w3.org>
- Message-ID: <CACfsppDr6D_THTFc7CYnD3zvEj+F391S6DJKxk9uwTY1LO2oQA@mail.gmail.com>
> I'd rather not add something to CSS that is all but impossible to author by hand. The sort of tweens that would be simple to author by hand would be for shapes that are simple to create by hand. Any complicated shape you try and tween would probably be complicated to tween manually - no matter the algorithm. Massaging the two paths into a form that produces a desirable tween effect is the job of a third party tool IMO. I just don't think complex tweening algorithms belong in the SVG standard. And given that even the proposal to include simple regular polygons in SVG2 was regarded as bloat, I doubt this would get past the approval process anyway. On 4 June 2015 at 18:26, Brian Birtles <bbirtles@mozilla.com> wrote: > On 2015/06/04 14:48, Paul LeBeau wrote: > >> Brian wrote: >> > When you actually go to author content though, you very often need >> anchor points or some way of describing *how* you want to go from A to B. >> >> >> That's true, but I don't think that is something an SVG renderer should >> need to worry about. >> > > If we're going to be doing segment normalization and subdivision already > (as Shane suggested), it's a small step from there to support anchor points. > > You suggested tools could easily adjust the src and dest paths, so what's > your concern with having the SVG user agent do that? > > I'd rather not add something to CSS that is all but impossible to author > by hand. >
Received on Thursday, 4 June 2015 11:11:39 UTC