Extension subsystem - Revision history

Moini at 19:54, 3 February 2023

2023-02-03T19:54:33Z

← Older revision		Revision as of 19:54, 3 February 2023
Line 1:		Line 1:
	[[Category:Extensions]]		[[Category:Extensions]]

			{{Template:MovedToOtherSite\|topic=Extension development\|new_url=https://inkscape.gitlab.io/extensions/documentation/\|new_site=GitLab}}

			----

	== General ==		== General ==
	The Extension system is a way to add functionality to Inkscape. The		The Extension system is a way to add functionality to Inkscape. The

Patrick87: /* Implementation Types */ mention plugins

2019-09-19T20:38:06Z

Implementation Types: mention plugins

← Older revision		Revision as of 20:38, 19 September 2019
Line 19:		Line 19:
	== Implementation Types ==		== Implementation Types ==
	While the functionality that the extension provides is described above, how that gets done is a different story. The Inkscape extensions system allows for programmers to implement their extension in a variety of ways, trying to match their particular skillset.		While the functionality that the extension provides is described above, how that gets done is a different story. The Inkscape extensions system allows for programmers to implement their extension in a variety of ways, trying to match their particular skillset.
	* '''Internal.''' Any extension type can be ~~implement~~ in C or C++ and directly linked into the Inkscape codebase. While in general the goal is to move as much out of the main Inkscape binary, this makes sense for many extensions including things like SVG input/output.		* '''Internal.''' Any extension type can be implemented in C or C++ and directly linked into the Inkscape codebase. While in general the goal is to move as much out of the main Inkscape binary, this makes sense for many extensions including things like SVG input/output.
			* '''Plugins.''' Similar to internal extensions (can be implement in C or C++) but linked as a separate library that is dynamically loaded at runtime.
	* '''Scripts.''' Scripts are where Inkscape uses standard in and standard out on an external executable to implement the functionality. This allow Inkscape to reuse a variety of utilities that already do format conversion or implement cool things in SVG. Typically the scripts that are effects use a SVG DOM library in their programming language of choice.		* '''Scripts.''' Scripts are where Inkscape uses standard in and standard out on an external executable to implement the functionality. This allow Inkscape to reuse a variety of utilities that already do format conversion or implement cool things in SVG. Typically the scripts that are effects use a SVG DOM library in their programming language of choice.
	* '''XSLT.''' This implementation is done in the XSLT language, and uses libxml's XSLT parser that is already linked with Inkscape.		* '''XSLT.''' This implementation is done in the XSLT language, and uses libxml's XSLT parser that is already linked with Inkscape.

Moini: /* See Also */

2017-03-19T16:32:37Z

~suv: /* See Also */

2014-12-15T02:12:25Z

~suv: /* See Also */ update link to current trunk repo

2014-12-15T01:19:39Z

See Also: update link to current trunk repo

← Older revision		Revision as of 01:19, 15 December 2014
Line 33:		Line 33:
	* [[MakingAnINX]]: every Extension needs an INX file.		* [[MakingAnINX]]: every Extension needs an INX file.
	* [http://sourceforge.net/mailarchive/message.php?msg_id=15742559\|A message from Ted Gould] describing the functionality and implementation types.		* [http://sourceforge.net/mailarchive/message.php?msg_id=15742559\|A message from Ted Gould] describing the functionality and implementation types.
	* [http://~~inkscape.svn~~.~~sourceforge~~.net/~~viewvc/~~inkscape/inkscape/trunk/doc/extension_system.txt~~?view=markup~~ The original extension architecture document from inkscape svn.] It would be good to look through this document and move pertinent facts onto this page.		* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/doc/extension_system.txt The original extension architecture document from inkscape svn.] It would be good to look through this document and move pertinent facts onto this page.

Tweenk: moved ExtensionArchitecture to Extension subsystem: kill wikiwords

2009-06-19T15:56:41Z

moved ExtensionArchitecture to Extension subsystem: kill wikiwords

← Older revision

Revision as of 15:56, 19 June 2009

Vsi: /* Maturity */

2007-12-19T05:32:29Z

Maturity

← Older revision		Revision as of 05:32, 19 December 2007
Line 27:		Line 27:
	The extension system is currently able to provide functionality from the '''Input''', '''Output''', and '''Effects''' categories. A plan has been scoped for the implementation of '''Path Effects''' but work has not yet begun. I am not aware of the status of the '''Tools''' functionality described above.		The extension system is currently able to provide functionality from the '''Input''', '''Output''', and '''Effects''' categories. A plan has been scoped for the implementation of '''Path Effects''' but work has not yet begun. I am not aware of the status of the '''Tools''' functionality described above.

	'''Internal''' and '''Script''' implementations are available to the developer. Bob Jamison (aka ishmal) has done a large amount of work toward '''DOM Scripts''' but there are not yet any working examples. I am not aware of the status of the '''XSLT''' implementation. '''Note:''' XSLT appears to support input and output filtering, but not effects filters (i.e. there is no implementation of Inkscape::Extension::Implementation::XSLT::effect(), only ::open() and ::save() )		'''Internal''' and '''Script''' implementations are available to the developer. Bob Jamison (aka ishmal) has done a large amount of work toward '''DOM Scripts''' but there are not yet any working examples. I am not aware of the status of the '''XSLT''' implementation. '''Note:''' XSLT at this time appears to support input and output filtering, but not effects filters (i.e. there is no implementation of Inkscape::Extension::Implementation::XSLT::effect(), only ::open() and ::save() )

	== See Also ==		== See Also ==

Vsi: /* Maturity */

2007-12-19T05:32:05Z

Maturity

← Older revision		Revision as of 05:32, 19 December 2007
Line 27:		Line 27:
	The extension system is currently able to provide functionality from the '''Input''', '''Output''', and '''Effects''' categories. A plan has been scoped for the implementation of '''Path Effects''' but work has not yet begun. I am not aware of the status of the '''Tools''' functionality described above.		The extension system is currently able to provide functionality from the '''Input''', '''Output''', and '''Effects''' categories. A plan has been scoped for the implementation of '''Path Effects''' but work has not yet begun. I am not aware of the status of the '''Tools''' functionality described above.

	'''Internal''' and '''Script''' implementations are available to the developer. Bob Jamison (aka ishmal) has done a large amount of work toward '''DOM Scripts''' but there are not yet any working examples. I am not aware of the status of the '''XSLT''' implementation. 'Note:' '''XSLT~~'''~~ appears to support input and output filtering, but not effects filters (i.e. there is no implementation of Inkscape::Extension::Implementation::XSLT::effect(), only ::open() and ::save() )		'''Internal''' and '''Script''' implementations are available to the developer. Bob Jamison (aka ishmal) has done a large amount of work toward '''DOM Scripts''' but there are not yet any working examples. I am not aware of the status of the '''XSLT''' implementation. '''Note:''' XSLT appears to support input and output filtering, but not effects filters (i.e. there is no implementation of Inkscape::Extension::Implementation::XSLT::effect(), only ::open() and ::save() )

	== See Also ==		== See Also ==

Vsi: /* Maturity */

2007-12-19T05:30:55Z

Maturity

← Older revision		Revision as of 05:30, 19 December 2007
Line 27:		Line 27:
	The extension system is currently able to provide functionality from the '''Input''', '''Output''', and '''Effects''' categories. A plan has been scoped for the implementation of '''Path Effects''' but work has not yet begun. I am not aware of the status of the '''Tools''' functionality described above.		The extension system is currently able to provide functionality from the '''Input''', '''Output''', and '''Effects''' categories. A plan has been scoped for the implementation of '''Path Effects''' but work has not yet begun. I am not aware of the status of the '''Tools''' functionality described above.

	'''Internal''' and '''Script''' implementations are available to the developer. Bob Jamison (aka ishmal) has done a large amount of work toward '''DOM Scripts''' but there are not yet any working examples. I am not aware of the status of the '''XSLT''' implementation.		'''Internal''' and '''Script''' implementations are available to the developer. Bob Jamison (aka ishmal) has done a large amount of work toward '''DOM Scripts''' but there are not yet any working examples. I am not aware of the status of the '''XSLT''' implementation. 'Note:' '''XSLT''' appears to support input and output filtering, but not effects filters (i.e. there is no implementation of Inkscape::Extension::Implementation::XSLT::effect(), only ::open() and ::save() )

	== See Also ==		== See Also ==

Colin Marquardt: Reverted edits by ZlvGbb (Talk); changed back to last version by Ryanlerch

2007-04-20T15:48:07Z

Reverted edits by ZlvGbb (Talk); changed back to last version by Ryanlerch

← Older revision		Revision as of 15:48, 20 April 2007
Line 19:		Line 19:
	== Implementation Types ==		== Implementation Types ==
	While the functionality that the extension provides is described above, how that gets done is a different story. The Inkscape extensions system allows for programmers to implement their extension in a variety of ways, trying to match their particular skillset.		While the functionality that the extension provides is described above, how that gets done is a different story. The Inkscape extensions system allows for programmers to implement their extension in a variety of ways, trying to match their particular skillset.
	* '''Internal.''' Any extension type can be implement in C or C and directly linked into the Inkscape codebase. While in general the goal is to move as much out of the main Inkscape binary, this makes sense for many extensions including things like SVG input/output.		* '''Internal.''' Any extension type can be implement in C or C++ and directly linked into the Inkscape codebase. While in general the goal is to move as much out of the main Inkscape binary, this makes sense for many extensions including things like SVG input/output.
	* '''Scripts.''' Scripts are where Inkscape uses standard in and standard out on an external executable to implement the functionality. This allow Inkscape to reuse a variety of utilities that already do format conversion or implement cool things in SVG. Typically the scripts that are effects use a SVG DOM library in their programming language of choice.		* '''Scripts.''' Scripts are where Inkscape uses standard in and standard out on an external executable to implement the functionality. This allow Inkscape to reuse a variety of utilities that already do format conversion or implement cool things in SVG. Typically the scripts that are effects use a SVG DOM library in their programming language of choice.
	* '''XSLT.''' This implementation is done in the XSLT language, and uses libxml's XSLT parser that is already linked with Inkscape.		* '''XSLT.''' This implementation is done in the XSLT language, and uses libxml's XSLT parser that is already linked with Inkscape.

← Older revision		Revision as of 16:32, 19 March 2017
Line 34:		Line 34:
	* [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/16210 A message from Ted Gould] describing the functionality and implementation types.		* [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/16210 A message from Ted Gould] describing the functionality and implementation types.
	* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/doc/extension_system.txt The original extension architecture document from inkscape svn.] It would be good to look through this document and move pertinent facts onto this page.		* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/doc/extension_system.txt The original extension architecture document from inkscape svn.] It would be good to look through this document and move pertinent facts onto this page.
			* [[Extension_Interpreters \| Extension Interpreters]] for info about supported interpreters and how to deal with different interpreter versions

← Older revision		Revision as of 02:12, 15 December 2014
Line 30:		Line 30:

	== See Also ==		== See Also ==
	* [[ScriptingHOWTO]]: an ~~explaination~~ of the details for creating an extension with the Script implementation.		* [[ScriptingHOWTO]]: an explanation of the details for creating an extension with the Script implementation.
	* [[MakingAnINX]]: every Extension needs an INX file.		* [[MakingAnINX]]: every Extension needs an INX file.
	* [http://~~sourceforge~~.~~net~~/~~mailarchive~~/~~message.php?msg_id=15742559\|~~A message from Ted Gould] describing the functionality and implementation types.		* [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/16210 A message from Ted Gould] describing the functionality and implementation types.
	* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/doc/extension_system.txt The original extension architecture document from inkscape svn.] It would be good to look through this document and move pertinent facts onto this page.		* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/view/head:/doc/extension_system.txt The original extension architecture document from inkscape svn.] It would be good to look through this document and move pertinent facts onto this page.