- From: Alex Danilo <alex@abbra.com>
- Date: Tue, 26 Jul 2011 10:47:21 +1000
- To: Cameron McCormack <cam@mcc.id.au>
- Cc: Leonard Rosenthol <lrosenth@adobe.com>, Vincent Hardy <vhardy@adobe.com>, Dirk Schulze <dirk@dschulze.com>, SVG WG <public-svg-wg@w3.org>
Hey Cam, --Original Message--: >Leonard Rosenthol: >> So in this case, the second segment in the examples would NOT render >> in existing implementations – and (IMO) that would be BAD (as it's >> data loss). > >I don’t see what the problem is with this. Even if we did have a path >syntax error behaviour that meant that the R/F commands ignored and the >following segments are still rendered, the shape is going to be wrong. >If we want to, we could have a feature string so that authors could have >a fallback path using <switch>. Just to throw in a completely off the proposal idea: What if this was all done using the superpath ideas such as presented at SVG/Open last year? ie. you have a super-path that has children which each form a segment of the path. Now if each of the child path segments were relative, then you could achieve the rotation of the end line you wanted just by animating the sub-path with a rotate, etc. This leverages the existing animation engines already in place and might be a far simpler solution to achieve what you're trying to do whilst adding the super-paths which lots of people have been asking for. Alex >-- >Cameron McCormack ≝ http://mcc.id.au/ > > >
Received on Tuesday, 26 July 2011 00:48:02 UTC