I would like to invite to fill the chart I've made. All you have write rights I
think.
I won't start any code string substitution until the chart is filled and agreed
:-P
https://docs.google.com/spreadsheet/ccc?key=0Ah8g_H3f7qpZdDR1N0piUThqZ0pySjh3eERzMjBDQVE
Zelgadis wrote:
--------------------
2012/5/22 Carlos Lopez Gonzalez <carloslopezgonza...@yahoo.es>:
> ...if we rename Duck to
> Control point we should say: "Then the user should select all the Curve
> point's Control points" instead of "Then the user selects all the BLine
> point's Ducks.".
> ...
> BLine point: Derived from above. We currently talk about BLine point's
> tangent duck as something easy to find and understand. Translated it would
> be: "Curve point's tangent Control point" too many points in my opinion.
> "Spline Item tangent's handle" sounds better to me. Well, everything sounds
> strange to me now! ^__^''
Let's don't make things too complicated. I don't remember such strange
phrases like "Then the user selects all the BLine point's Ducks." in
documentation. Even if we have such ones, let's avoid them. Keep it
simple: "User should select a vertex together with its tangents". Or:
"User should select a vertex together with its tangent and width
handles". It's just a matter of good writing style. ^__^
In fact BLinePoint is a kind of internal concept that visible to user
only as the parameter type. He needs that definition only in
export/linking operation to distinguish vertex (as BLine Point
element) from the whole Bline point. We don't have "BLine Points" list
- it's called "Vertices". So we shouldn't use the BlinePoint in user
documentation very much.
--------------------
I have to disagree on that. For bones BLine Point concept is very important
because it will appear converted to a new type: Bone Influence type.
The BLine point (vertex and tangents together) will be under a new type that
has the influence of bones. Also, vertex individually can be bone influenced
alone. So for good or bad, the concept of BLine point should be defined and
documented.
Zelgadis wrote:
-----------------------------
Anyway we will need to replace BLine point with something. I don't
like "Spline Point" (I assume that "BLine" replaced to "Spline" here).
Because Point is looks like a point on the Spline (x,y), not a set of
elements. "Spline Item" is better but still clumsy. Let's look at the
illustration (what we have now) -
http://img254.imageshack.us/img254/982/20120522001.png
It's obvious that "Bline Point" type is referenced as "Vertex"
everywhere. Except one inconsistency - where "vector" type is called
"Vertex" too for some reason.
My proposal:
"Bline Point" -> "Vertex" (as set of elements)
"Vertex" (as sub-parameter of BLine Point) -> "Point"
See illustration with changes:
http://img543.imageshack.us/img543/9751/201205220012.png
-------------------------
Vertex sounds ok but, what about the confusion with the Polygon vertices?
To use Vertex to a Polygon is perfect by dictionary vertex definition but since
the
Spline, BLine or whatever we call it is something special, we need to use a
special
word.
Point is ok as sub parameter of blinepoint or vertex or whatever. Point is
exactly that: a (x,y) location.
Zelgadis wrote:
-----------------------------
2012/5/22 Carlos Lopez Gonzalez <carloslopezgonza...@yahoo.es>:
> Regarding to renaming implementation process I think that we should do it in
> one shot but without hurry up due to a new release. I don't plan to do a
> release soon. Unless someone come with some substantial commits and it
> deserves a release, the next release is planned with the new Cairo
> implementation as main change so it will take a while at the moment.
I think that we should do changes and release with new terminology
even if we have no new features.
This will indicate a new step - reworked terminology. In fact I DO
prefer to release WITHOUT new features, because we should do release
and documentation change in sync and quick - and that's a lot of work.
If we will have new features - the it will be too much for me to
handle at one shot. Sorry.
---------------------
It is ok. Now I understand.
Cheers
Carlos
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Synfig-devl mailing list
Synfig-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synfig-devl
