I'm not going to be able to get to work on adding tooltips and descriptions to the effects until much later this evening. If someone else has time to look at it great. Otherwise it would be a real jump start just to get people to list the effects that they think require more explaination. Unfortunately some of the effects that might require the most explaination don't pop up an autogui to display it (eg envelope), this just occured to me.
-Function Plotter needs to say that it requires a selected <rect/> -Random Tree needs to say that the result will be off canvas -Fractal (L-System) needs to say that the result will be off canvas -?
Aaron Spike
On 5/27/06, Aaron Spike <aaron@...749...> wrote:
-Random Tree needs to say that the result will be off canvas -Fractal (L-System) needs to say that the result will be off canvas
Wouldn't it be easier to just fix these? My proposal was to add command line params passed to all effects that would give:
- selection bbox
- the view area box
- current layer
and fix the python scripts to use this info. (By the way, then the function plotter would not require only a rect - it will be able to use the bbox of any selection instead.)
To me, the wrong layer/position of the effect output looks like a bug well worth fixing in our bugfix drive :)
On Sat, 27 May 2006, Aaron Spike wrote:
Date: Sat, 27 May 2006 09:02:20 -0500 From: Aaron Spike <aaron@...749...> To: inkscape inkscape-devel@lists.sourceforge.net Subject: [Inkscape-devel] effects and impending string freeze
I'm not going to be able to get to work on adding tooltips and descriptions to the effects until much later this evening. If someone else has time to look at it great. Otherwise it would be a real jump start just to get people to list the effects that they think require more explaination. Unfortunately some of the effects that might require the most explaination don't pop up an autogui to display it (eg envelope), this just occured to me.
-Function Plotter needs to say that it requires a selected <rect/>
I know that will get really annoying (from my experience with that well known graphics program). If there is no selection then the scripts should be smarter and use the page area or select all and use that space.
-Random Tree needs to say that the result will be off canvas -Fractal (L-System) needs to say that the result will be off canvas -?
why put them off canvas? why not put them right where the user is currently looking, and if necessary as a seperate group/layer? (if they are not doing this already i would generally expect any effect to return one single object or group and leave it to users to break it apart later if they want. the alternative of dumping multiple objects and requiring users to remember to group them before accidentally clicking something else is too awkward)
participants (3)
-
Aaron Spike -
Alan Horkan -
bulia byak