Difference between revisions of "BlueprintUIGradientFill"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
== TODO == | == TODO == | ||
== Discussion == | == Discussion == | ||
<ul> | |||
<li>Inkscape Forum (Inkscape ideas) | |||
<br /> | |||
http://www.inkscapeforum.com/viewtopic.php?f=28&t=8709 | |||
</li> | |||
<li>Launchpad | |||
<br /> | |||
https://bugs.launchpad.net/bugs/722017 | |||
</li> | |||
</ul> | |||
Revision as of 23:00, 21 February 2011
Summary
A user interface which allows for simpler management of gradients, better gradient organization and simplification of the interface.
Rationale
1. Merging the Gradient editor window and the Fill and Stroke Gradient window into one window. Advantages:
- Reduces real estate and moves the gradient editor off the canvas.
- The list allows the user to delete gradients whether they are being used or not.
- Search now works, this allows quick selection of gradients when the gradient list becomes large.
Design
UI
Workflow
Usage
SVG representation
TODO
Discussion
- Inkscape Forum (Inkscape ideas)
http://www.inkscapeforum.com/viewtopic.php?f=28&t=8709 - Launchpad
https://bugs.launchpad.net/bugs/722017