Difference between revisions of "Plugin Architecture"

From Scribus Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 +
{{Scripting Index}}
 +
 
Scribus can be extended and automated using C++ plugins. Plugins are dynamic loaded libraries in "so" format.
 
Scribus can be extended and automated using C++ plugins. Plugins are dynamic loaded libraries in "so" format.
  

Revision as of 20:55, 5 February 2005

This article is part of the Scripts series.

Scribus can be extended and automated using C++ plugins. Plugins are dynamic loaded libraries in "so" format.

An introduction to writing Scribus plugins is available here: [http://docs.scribus.net/index.php?lang=en&sm=pluginhowto&page=plugin_howto]. At present (3 Feb '05) there's not a lot of documentation available for the object model. It's said to be in Doxygen format in the source code, although I can't find it.

There is also a separate api for formatted text importer plugins. More information on this can be found from here: [http://docs.scribus.net/index.php?lang=en&sm=gettexthowto&page=gettexthowto]

Scribus also provides a Python Scripter API, which is generally easier to use, more mature and better documented than the C++ API.