|Ulrich Laesche||Nov 7, 2007 5:15 am||.doc|
|Bezaire, Benoit||Nov 7, 2007 8:15 am|
|Lofton Henderson||Nov 30, 2007 2:48 pm|
|Bezaire, Benoit||Dec 13, 2007 5:34 am|
|Weidenbrueck, Dieter||Dec 13, 2007 5:37 am|
|Lofton Henderson||Dec 13, 2007 11:45 am|
|Lofton Henderson||Dec 17, 2007 10:32 am|
|Weidenbrueck, Dieter||Dec 18, 2007 1:13 am|
|Lofton Henderson||Jan 2, 2008 4:47 pm|
|Cruikshank, David W||Jan 3, 2008 8:33 am|
|Lofton Henderson||Jan 3, 2008 10:41 am|
|Lofton Henderson||Jan 3, 2008 3:33 pm|
|Cruikshank, David W||Jan 3, 2008 4:01 pm|
|Galt, Stuart A||Jan 4, 2008 9:54 am|
|Lofton Henderson||Jan 5, 2008 10:00 am|
|Weidenbrueck, Dieter||Jan 14, 2008 1:52 am|
|Weidenbrueck, Dieter||Jan 14, 2008 1:57 am|
|Galt, Stuart A||Jan 18, 2008 9:33 am|
|Weidenbrueck, Dieter||Jan 18, 2008 9:42 am|
|Galt, Stuart A||Jan 18, 2008 10:30 am|
|Weidenbrueck, Dieter||Jan 18, 2008 10:52 am|
|Galt, Stuart A||Jan 18, 2008 12:31 pm|
|Lofton Henderson||Jan 19, 2008 3:46 pm|
|Lofton Henderson||Jan 21, 2008 9:45 am|
|Weidenbrueck, Dieter||Jan 21, 2008 10:55 am|
|Subject:||WG: transform proposal 2|
|From:||Ulrich Laesche (ulr...@ematek.de)|
|Date:||Nov 7, 2007 5:15:33 am|
doc00001.doc - 37k
As a reply to Benoit's two mails (Thanks for that, Benoit) attached please find the response from our develoment team as well as an updated transform spec.
1. Yes, we replaced "move" by "translate". Also, we replaced the absolute coordinates for the new location by distances. This means we just move relatively to the old position. That's how it's done in SVG.
2. We would like to use the additive transformation. Only in this way we can do some complex transformations using a chain of the simple transformations, like scale down by 1/2, move to the right by 3 and up by 5, and rotate clockwise by 35 degrees. If it would be "replace" then we would not be able to do these transformations, as we should start always from the beginning.
May be we should add a new API function, like finishTransformation(). For example, if we want to show only the final position, and not the intermediate: scale(1/2,1/2) translate(3,5) rotate(35) finishTransform()
3. Rotate - yes, we introduced the origin for convenience, see spec. However, we could always rotate around the center and then move (see 2).
4. Scale - no, we don't need the origin point. If the element has the w,h=4,6 and we scale 1/2, then the new size would be w1,h1=2,3 and the same origin. Then you can translate to the new position using translate API.
5. Yes, Transform was an attempt to do a motion along the path, but it appears to be more complicated and does not fit the budget approach, so we drop it for now.
6.Rotation is clockwise, if angle > 0, and counterclockwise if < 0.
7.Yes, the scale can be > 0, then it's zoom-in, and < 0, then it's zoom-out.
-----Ursprüngliche Nachricht----- Von: Bezaire, Benoit [mailto:bbez...@ptc.com] Gesendet: Mittwoch, 24. Oktober 2007 21:19 An: CGM Open WebCGM TC Betreff: [cgmo-webcgm] Feedback on transform proposal (was RE: [cgmo-webcgm] Telecon REMINDER - agenda)
Here is more feedback on the transform proposal...
About the move() API... why is this not a translate() API? Is there a specific reason? I ask because a translate can be expressed in a 3x3 matrix, a move can't.
About the scale() API... can x/y be negative? i.e., mirror or do we stick with > 0? (note a center point is also needed here, same as rotation question)
About the transform() API... I'm not sure I understand. We see parameters a..f similar to a 3x3 matrix, but the description talks about a motion path? Are we attempting to do a general matrix transform, or is the intent to do a motion along a path? We talked about both, that's why I'm asking.
Kind regards, Benoit.
Visible links 1. mailto:bbez...@ptc.com