2012/5/22 Carlos Lopez Gonzalez <[email protected]>: > 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
Nice! Very cool! ^__^ > Zelgadis wrote: > -------------------- > > 2012/5/22 Carlos Lopez Gonzalez <[email protected]>: >> ...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. "we shouldn't use the BlinePoint in user documentation very much" = we WILL use it, but not much. ^__^ > 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. >From user point of view Polygon Vertex is simplified case of Spline Vertex. > Point is ok as sub parameter of blinepoint or vertex or whatever. Point is > exactly that: a (x,y) location. I also have another idea - we can use "Origin" instead of "Point". I.e. "Origin of Vertex/Spline Item" like "Origin of Group (PasteCanvas) layer". When referencing ducks it's ok to use "Vertex handle" instead of "Vertex Origin". In fact, even in current documentation we use simple constructions: * If you want to remove a vertex, right click on it and select "Delete Vertex". * If you want to manipulate the vertices after you have created the layers, it is very easy to do so. (http://wiki.synfig.org/wiki/Doc:Creating_Shapes) BTW, try to replace"vertex" with "spline item" in sentences above and you'll get a bit clumsy results. Well, after reading the documentation I still come to conclusion that "control point" is still better than "handle". Let's see by example from the same page: * Despite the fact that they are two separate layers, their vertices parameter has already been linked — so you can select either one and move its ducks around and the other one will also change. * You do this by selecting the outline layer and tweaking with the width ducks. * If brown ducks are in your way, you can hide them by clicking the "Toggle vertex ducks" button at the top of the canvas window (the second one from the left). Replacing "ducks" with "control points" make it sound better than "handles" for my taste. K. -- http://morevnaproject.org/ ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/synfig-devl
