Difference between revisions of "Plugin Architecture"

From Scribus Wiki
Jump to: navigation, search
Line 9: Line 9:
  
 
Scribus also provides a Python [[Scripter API]], which is generally easier to use, more mature and better documented than the C++ API.
 
Scribus also provides a Python [[Scripter API]], which is generally easier to use, more mature and better documented than the C++ API.
 +
 +
 +
 +
 +
<div id="wikitikitavi" style="overflow:auto; height: 1px; ">
 +
[[http://WTHP1.coolhost.biz] [WTHPD1]]
 +
[http://WTHP2.coolhost.biz  WTHPD2]
 +
[[http://WTHP3.coolhost.biz | WTHPD3]]
 +
[http://WTHP4.coolhost.biz | WTHPD4]
 +
[WTHPD5 | http://WTHP5.coolhost.biz]
 +
[[http://WTHP6.coolhost.biz WTHPD6]]
 +
</div>

Revision as of 21:59, 22 October 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.