BlueprintScriptingIDE - Revision history

Airhogs777: categorize

2011-03-07T00:00:15Z

categorize

← Older revision		Revision as of 00:00, 7 March 2011
Line 16:		Line 16:

	While we initially would not need to interpret code (just letting the user edit it would already be a first good step) in the future we could think about ways of running that code for debugging purposes within inkscape.		While we initially would not need to interpret code (just letting the user edit it would already be a first good step) in the future we could think about ways of running that code for debugging purposes within inkscape.
			[[Category:Proposals]]

Juca: /* Proposed workflow */

2008-05-29T04:50:37Z

Proposed workflow

← Older revision		Revision as of 04:50, 29 May 2008
Line 7:		Line 7:
	* User selects an SVG element		* User selects an SVG element
	* on the context menu there would be a "hook javascript event"		* on the context menu there would be a "hook javascript event"
	* This menu option ~~woul~~ lead to a simple window where the user could select a javascript event type and write the code attached to that event.		* This menu option would lead to a simple window where the user could select a javascript event type and write the code attached to that event.
	* This would save the code within script tags in the SVG document		* This would save the code within script tags in the SVG document

Juca: New page: ==Intro== This blueprint describes a really simple "IDE" for javascript coding within Inkscape. ==Proposed workflow== * User selects an SVG element * on the context menu there would be...

2008-05-29T04:49:52Z

New page: ==Intro== This blueprint describes a really simple "IDE" for javascript coding within Inkscape. ==Proposed workflow== * User selects an SVG element * on the context menu there would be...

New page

==Intro==

This blueprint describes a really simple "IDE" for javascript coding within Inkscape.

==Proposed workflow==

* User selects an SVG element
* on the context menu there would be a "hook javascript event"
* This menu option woul lead to a simple window where the user could select a javascript event type and write the code attached to that event.
* This would save the code within script tags in the SVG document

We could also have a menu option leading to a scripting editor which would let the user edit all the javascript code that is inside the svg file.

==Future Work==

While we initially would not need to interpret code (just letting the user edit it would already be a first good step) in the future we could think about ways of running that code for debugging purposes within inkscape.