Readability of user visible messages
Hi,
It would be great if somebody for whom English is a native language could go through user visible messages and take care of those unclear of them. I'm specifically referring to live paths effects, which is full of things that are difficult to understand.
For instance, Celtic Knot has two options: "add stroke width to interruption size" and "add other's stroke width to interruption size".
And we still have a lot of places where it's not clear in what units of measure the function works. "Fuse nearby ends" in Pattern Along Path LPE is one of them. Varios SVG Filter primitives too...
Would be great to have that sorted out before strings freeze.
Alexandre
Alexandre Prokoudine wrote:
It would be great if somebody for whom English is a native language could go through user visible messages and take care of those unclear of them. I'm specifically referring to live paths effects, which is full of things that are difficult to understand.
I have recently corrected some extensions for this very reason (there were some blatantly obvious mistakes) and could look into some further. Unfortunately, though I live in England I am only a nearly-native speaker ;-) so indeed someone else's watchful eye would be handy. I am happy to change the source code though...
Regards, Marcin
On Tue, 2009-06-09 at 16:08 +0400, Alexandre Prokoudine wrote:
Hi,
It would be great if somebody for whom English is a native language could go through user visible messages and take care of those unclear of them. I'm specifically referring to live paths effects, which is full of things that are difficult to understand.
For instance, Celtic Knot has two options: "add stroke width to interruption size" and "add other's stroke width to interruption size".
For the Knot effect, currently:
[] Is visible Interruption width [ ] [] unit of stroke width [] add stroke width to interruption size [] add other's stroke width to interruption size Switcher size [ ]
I propose:
[] Is visible ----------------------- Path gap is sum of: Fixed width [ ] [] in Units of stroke width [] Stroke width [] Crossing path stroke width ----------------------- Switcher size [ ]
If no one objects or has a better suggestion, I will attempt to make these changes.
Tav
On Thu, Jun 18, 2009 at 1:57 PM, Tavmjong Bah wrote:
I propose:
[] Is visible
Path gap is sum of: Fixed width [ ] [] in Units of stroke width [] Stroke width [] Crossing path stroke width
Switcher size [ ]
Looks good to me. However, "Is visible" is supposed to be removed as agreed earlier since it duplicates the eye icon in the effects stack.
Alexandre
Great!! thanks a lot! that is much better. :-) I'm pretty happy someone fixed this: I just can't write friendly UI, even in french ;-) Please please please, have a look at my other lpes (sketch, hatches, vonkoch...) they are in the same poor state!! :-( I kept asking for help on IRC but had only little feed back.
Rk: in the knot lpe, "crossing path's stroke width" is mainly interesting when the effect is applied to a group, but this is still a bit buggy: all the changes in the crossings are lost as soon as you node-edit a group member. This might be easy to fix, but requires some understanding of internal architecture involved (a 'array' parameter is not initalized as it should)... any help appreciated!
cheers! jfb.
2009/6/18 Tavmjong Bah <tavmjong@...8...>
On Tue, 2009-06-09 at 16:08 +0400, Alexandre Prokoudine wrote:
Hi,
It would be great if somebody for whom English is a native language could go through user visible messages and take care of those unclear of them. I'm specifically referring to live paths effects, which is full of things that are difficult to understand.
For instance, Celtic Knot has two options: "add stroke width to interruption size" and "add other's stroke width to interruption size".
For the Knot effect, currently:
[] Is visible Interruption width [ ] [] unit of stroke width [] add stroke width to interruption size [] add other's stroke width to interruption size Switcher size [ ]
I propose:
[] Is visible
Path gap is sum of: Fixed width [ ] [] in Units of stroke width [] Stroke width [] Crossing path stroke width
Switcher size [ ]If no one objects or has a better suggestion, I will attempt to make these changes.
Tav
Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, 2009-06-18 at 15:23 +0200, jf barraud wrote:
Great!! thanks a lot! that is much better. :-) I'm pretty happy someone fixed this: I just can't write friendly UI, even in french ;-) Please please please, have a look at my other lpes (sketch, hatches, vonkoch...) they are in the same poor state!! :-( I kept asking for help on IRC but had only little feed back.
Rk: in the knot lpe, "crossing path's stroke width" is mainly interesting when the effect is applied to a group, but this is still a bit buggy: all the changes in the crossings are lost as soon as you node-edit a group member. This might be easy to fix, but requires some understanding of internal architecture involved (a 'array' parameter is not initalized as it should)... any help appreciated!
cheers! jfb.
I've taken a quick look at the code. It seems that the parameter list in the GUI is automatically generated when one calls registerParameter(). Is there a way to add a text line in the GUI without creating a parameter? That would be quite useful, as would being able to add a simple line as a separator (i.e. separate Strokes section from Construction lines section).
Tav
I've taken a quick look at the code. It seems that the parameter list in the GUI is automatically generated when one calls registerParameter(). Is there a way to add a text line in the GUI without creating a parameter? That would be quite useful, as would being able to add a simple line as a separator (i.e. separate Strokes section from Construction lines section).
Tav
+1!
I believe this is not hard to add for people with better insight in UI related stuff, but it does not exist atm. I went around this issue in sketch by putting the "common" text in the first label, but this is no good solution :-(
jfb.
participants (4)
-
Alexandre Prokoudine -
jf barraud -
Marcin Floryan -
Tavmjong Bah