Inkscape/macrogoodness - Revision history

Kris: linkfix

2012-03-01T16:43:21Z

linkfix

← Older revision		Revision as of 16:43, 1 March 2012
Line 28:		Line 28:

	We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.		We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.
	- [[JonCruz]]		- [[User:JonCruz\|JonCruz]]

	We might want to look into using [[REX]] for macros.		We might want to look into using [[REX]] for macros.

Kris: linkfix

2012-03-01T16:41:15Z

linkfix

← Older revision		Revision as of 16:41, 1 March 2012
Line 25:		Line 25:

	Macros should try to be as intelligent as possible. That is do smart actions on objects as opposed to recording coordinate moves and clicks.		Macros should try to be as intelligent as possible. That is do smart actions on objects as opposed to recording coordinate moves and clicks.
	- [[JonCruz]]		- [[User:JonCruz\|JonCruz]]

	We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.		We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.

JonCruz: /* Discussion */

2007-02-19T21:39:07Z

Discussion

← Older revision		Revision as of 21:39, 19 February 2007
Line 29:		Line 29:
	We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.		We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.
	- [[JonCruz]]		- [[JonCruz]]

			We might want to look into using [[REX]] for macros.

	=== BUGS ===		=== BUGS ===

JonCruz: /* Discussion */

2007-02-19T21:32:52Z

Discussion

← Older revision		Revision as of 21:32, 19 February 2007
Line 22:		Line 22:

	Mental commented that it could be similar to how the Undo History Dialog works except it probably needs to be on a slightly higher level and we'd probably need richer tagging for the XML.		Mental commented that it could be similar to how the Undo History Dialog works except it probably needs to be on a slightly higher level and we'd probably need richer tagging for the XML.


			Macros should try to be as intelligent as possible. That is do smart actions on objects as opposed to recording coordinate moves and clicks.
			- [[JonCruz]]

			We really want macros to be replayable without a UI. So one could invoke Inkscape from the commandline, run headless and replay edits onto several documents.
			- [[JonCruz]]

	=== BUGS ===		=== BUGS ===

ScislaC: /* Basic Outline of Features/Functions */

2007-01-26T17:03:24Z

Basic Outline of Features/Functions

← Older revision		Revision as of 17:03, 26 January 2007
Line 2:		Line 2:

	=== Basic Outline of Features/Functions ===		=== Basic Outline of Features/Functions ===
	*Standard macro controls = Record, Play, Stop, New, and Delete (plus Save and Load)~~<br>~~		*Standard macro controls = Record, Play, Stop, New, and Delete (plus Save and Load)
	*New macros		*New macros
	**Create macros by recording		**Create macros by recording
	**Create macros from undo history		**Create macros from undo history
	**It's desirable to have the macros work contextually and include things such as selection (and also to include TABing to make context more useful)~~<br>~~		**It's desirable to have the macros work contextually and include things such as selection (and also to include TABing to make context more useful)
	*Play macros		*Play macros
	**Macros need to intelligently skip impossible steps (such as font size changes being applied to a path)		**Macros need to intelligently skip impossible steps (such as font size changes being applied to a path)
	**A spinbox next to play to tell it the number of times to play the macro (It should also give info to the status bar to say "playing macro n, X of Y scheduled times", or something like that)~~<br>~~		**A spinbox next to play to tell it the number of times to play the macro (It should also give info to the status bar to say "playing macro n, X of Y scheduled times", or something like that)
	*Saving/Loading macros		*Saving/Loading macros
	**Save macros to sets and load sets of macros		**Save macros to sets and load sets of macros
	**Optionally save macros only in the current document (stored in defs perhaps)~~<br>~~		**Optionally save macros only in the current document (stored in defs perhaps)
	**Documents should remember which sets they've had loaded and auto-load those when the document is re-opened		**Documents should remember which sets they've had loaded and auto-load those when the document is re-opened
	*Undo		*Undo

ScislaC: fleshed out the basics a bit

2007-01-26T16:59:51Z

fleshed out the basics a bit

← Older revision		Revision as of 16:59, 26 January 2007
Line 2:		Line 2:

	=== Basic Outline of Features/Functions ===		=== Basic Outline of Features/Functions ===
			*Standard macro controls = Record, Play, Stop, New, and Delete (plus Save and Load)<br>
			*New macros
			**Create macros by recording
			**Create macros from undo history
			**It's desirable to have the macros work contextually and include things such as selection (and also to include TABing to make context more useful)<br>
			*Play macros
			**Macros need to intelligently skip impossible steps (such as font size changes being applied to a path)
			**A spinbox next to play to tell it the number of times to play the macro (It should also give info to the status bar to say "playing macro n, X of Y scheduled times", or something like that)<br>
			*Saving/Loading macros
			**Save macros to sets and load sets of macros
			**Optionally save macros only in the current document (stored in defs perhaps)<br>
			**Documents should remember which sets they've had loaded and auto-load those when the document is re-opened
			*Undo
			**Undo should undo individual steps
			**Undo History Dialog should have a wrapper for "Played Macro", to easily step back to before it was played.

			=== Discussion ===
			Should macros be written in XML, or something else?<br><br>

			Mental commented that it could be similar to how the Undo History Dialog works except it probably needs to be on a slightly higher level and we'd probably need richer tagging for the XML.

	=== BUGS ===		=== BUGS ===

ScislaC: Create Page for Macro/Action Dialog Goodness

2007-01-26T15:58:06Z

Create Page for Macro/Action Dialog Goodness

New page

Macro/Action dialog goodness that Gustav and Josh are working on. As items are taken care of, they're removed from the main text of this page. The controls/features will be copied to the bottom of this page in temp release notes (they will be fleshed out prior to the 0.46 release). <br>

=== Basic Outline of Features/Functions ===

=== BUGS ===
Can't have bugs without code. ;)

=== Release Notes ===
Can't have release notes without code. :)