Inkscape/gradientgoodness - Revision history

ScislaC: /* Release Notes: */ - removed from page as all current notes have been moved accordingly

2007-04-16T01:21:38Z

Release Notes:: - removed from page as all current notes have been moved accordingly

← Older revision		Revision as of 01:21, 16 April 2007
Line 39:		Line 39:

	=== Release Notes: ===		=== Release Notes: ===
	~~Gradient Tool changes:~~		All current release notes are where they should be in main release notes for 0.46.
	*Stops in ~~gradients can be added, deleted, and edited on-canvas now.~~
	**Stops can be added by double clicking on the gradient line or by Ctrl+Alt+Click on the line.
	**Stops can be deleted by Ctrl+Alt+Click on a Stop or the delete key for ~~the selected stop(s)~~.
	**When you delete an end stop, the nearest stop becomes the new end.
	**When deleting an endstop and there are no intermediate stops, the object will be painted with the color/opacity of the remaining stop.
	**More than one stop can be selected at a time.
	***Can be moved together if next to each other.
	***Can be deleted at the same time.
	***When multiple gradient stops are selected, the selected style indicator (in the statusbar) displays and controls the [averaged!!!] color and opacity of the selected stops.

	=== Coming up next ? ===		=== Coming up next ? ===
	[[Inkscape/liveeffectsgoodness]]		[[Inkscape/liveeffectsgoodness]]

ScislaC: /* Release Notes: */

2007-04-16T01:16:11Z

Release Notes:

← Older revision		Revision as of 01:16, 16 April 2007
Line 44:		Line 44:
	**Stops can be deleted by Ctrl+Alt+Click on a Stop or the delete key for the selected stop(s).		**Stops can be deleted by Ctrl+Alt+Click on a Stop or the delete key for the selected stop(s).
	**When you delete an end stop, the nearest stop becomes the new end.		**When you delete an end stop, the nearest stop becomes the new end.
			**When deleting an endstop and there are no intermediate stops, the object will be painted with the color/opacity of the remaining stop.
	**More than one stop can be selected at a time.		**More than one stop can be selected at a time.
	***Can be moved together if next to each other.		***Can be moved together if next to each other.

ScislaC: /* Related List Discussion */

2007-04-16T01:14:25Z

Related List Discussion

← Older revision		Revision as of 01:14, 16 April 2007
Line 37:		Line 37:
	* Node moving by arrow keys currently does not work		* Node moving by arrow keys currently does not work
	* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.		* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.
	* <strike>The node deletion logic needs to be smarter. In particular:
	** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.</strike>

	=== Release Notes: ===		=== Release Notes: ===

Johanengelen: improved stop deletion

2007-04-01T21:34:22Z

improved stop deletion

← Older revision		Revision as of 21:34, 1 April 2007
Line 37:		Line 37:
	* Node moving by arrow keys currently does not work		* Node moving by arrow keys currently does not work
	* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.		* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.
	* The node deletion logic needs to be smarter. In particular:		* <strike>The node deletion logic needs to be smarter. In particular:
	** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.		** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.</strike>

	=== Release Notes: ===		=== Release Notes: ===

ScislaC: /* RFE: */

2007-03-29T17:44:26Z

RFE:

← Older revision		Revision as of 17:44, 29 March 2007
Line 20:		Line 20:
	*enable Ins key to create new midstops; if no gradient nodes selected, then add a new stop in the middle of each interval in the selected object gradient; if some midstops are selected, add new midstop(s) only between them (similar to how Ins works in Node tool)		*enable Ins key to create new midstops; if no gradient nodes selected, then add a new stop in the middle of each interval in the selected object gradient; if some midstops are selected, add new midstop(s) only between them (similar to how Ins works in Node tool)
	*"Drag and Drop" from the color palette		*"Drag and Drop" from the color palette
			**Drop on a stop to change color
			**Drop on the gradient line to add new stop

	=== BUGS: ===		=== BUGS: ===

ScislaC: /* Release Notes: */

2007-03-29T17:08:26Z

Release Notes:

← Older revision		Revision as of 17:08, 29 March 2007
Line 43:		Line 43:
	**Stops can be added by double clicking on the gradient line or by Ctrl+Alt+Click on the line.		**Stops can be added by double clicking on the gradient line or by Ctrl+Alt+Click on the line.
	**Stops can be deleted by Ctrl+Alt+Click on a Stop or the delete key for the selected stop(s).		**Stops can be deleted by Ctrl+Alt+Click on a Stop or the delete key for the selected stop(s).
			**When you delete an end stop, the nearest stop becomes the new end.
	**More than one stop can be selected at a time.		**More than one stop can be selected at a time.
	***Can be moved together if next to each other.		***Can be moved together if next to each other.

ScislaC: confirmed and removed fixed items

2007-02-14T16:34:00Z

confirmed and removed fixed items

← Older revision		Revision as of 16:34, 14 February 2007
Line 36:		Line 36:
	* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.		* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.
	* The node deletion logic needs to be smarter. In particular:		* The node deletion logic needs to be smarter. In particular:
	** <strike>when deleting an intermediate stop, do what you're doing now, no need to change
	** when deleting an endstop and there's at least one intermediate stop, shorten the gradient by making the closest intermediate stop the new endstop (you're doing it now but only for color/opacity; I think we should also change the position of the endstop by moving it to the position of the closest intermediate, in effect shortening the gradient line, so that the rest of the gradient does not change at all) </strike>
	** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.		** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.

Johanengelen: /* Related List Discussion */

2007-02-03T21:38:14Z

Related List Discussion

← Older revision		Revision as of 21:38, 3 February 2007
Line 34:		Line 34:
	I've played with it some, not too much, but here are some observations:<br>		I've played with it some, not too much, but here are some observations:<br>
	* Node moving by arrow keys currently does not work		* Node moving by arrow keys currently does not work
	* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. Can you try to move the core of that function into a GrDrag method and make only that method public? This would let us make a lot of other stuff in GrDrag private.		* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. <strike>Can you try to move the core of that function into a GrDrag method and make only that method public? </strike>This would let us make a lot of other stuff in GrDrag private.
	* The node deletion logic needs to be smarter. In particular:		* The node deletion logic needs to be smarter. In particular:
	** when deleting an intermediate stop, do what you're doing now, no need to change		** <strike>when deleting an intermediate stop, do what you're doing now, no need to change
	** when deleting an endstop and there's at least one intermediate stop, shorten the gradient by making the closest intermediate stop the new endstop (you're doing it now but only for color/opacity; I think we should also change the position of the endstop by moving it to the position of the closest intermediate, in effect shortening the gradient line, so that the rest of the gradient does not change at all)		** when deleting an endstop and there's at least one intermediate stop, shorten the gradient by making the closest intermediate stop the new endstop (you're doing it now but only for color/opacity; I think we should also change the position of the endstop by moving it to the position of the closest intermediate, in effect shortening the gradient line, so that the rest of the gradient does not change at all) </strike>
	** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.		** when deleting an endstop and there are no intermediate stops, remove the gradient and paint the object with the color/opacity of the other stop, not with black as now.

Bbb: /* Release Notes: */

2007-01-28T19:06:06Z

Release Notes:

← Older revision		Revision as of 19:06, 28 January 2007
Line 47:		Line 47:
	**More than one stop can be selected at a time.		**More than one stop can be selected at a time.
	***Can be moved together if next to each other.		***Can be moved together if next to each other.
	***Can be deleted at same time.		***Can be deleted at the same time.
	*When gradient stops are selected the ~~opacity spinbox~~ in the ~~status bar~~ controls ~~that~~ stops~~' alpha~~.		***When multiple gradient stops are selected, the selected style indicator (in the statusbar) displays and controls the [averaged!!!] color and opacity of the selected stops.

	=== Coming up next ? ===		=== Coming up next ? ===
	[[Inkscape/liveeffectsgoodness]]		[[Inkscape/liveeffectsgoodness]]

ScislaC: /* Related List Discussion */

2007-01-26T16:19:00Z

Related List Discussion

← Older revision		Revision as of 16:19, 26 January 2007
Line 32:		Line 32:
	=== Related List Discussion ===		=== Related List Discussion ===
	From bbyak...<br>		From bbyak...<br>
	I've played with it some, not too much, but here are some observations:~~<br>~~<br>		I've played with it some, not too much, but here are some observations:<br>
	* Node moving by arrow keys currently does not work		* Node moving by arrow keys currently does not work
	* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. Can you try to move the core of that function into a GrDrag method and make only that method public? This would let us make a lot of other stuff in GrDrag private.		* Let's try to make less of GrDrag public. The sp_gradient_context_delete_stops is especially intrusive. Can you try to move the core of that function into a GrDrag method and make only that method public? This would let us make a lot of other stuff in GrDrag private.