The team is mostly resident in Europe, so Central European Time evenings is when it is busiest. You will find #scribus usually lively during parts of each day. Probably 99% of the planning and project discussions take place there. As rule, we do not do a lot of planning or development discussion by e-mail, but by IRC. The documentation in the scplugin.h and pluginmanager.h help explain how the system works.įor any reasonable plugin idea, you will receive encouragement and assistance from the Scribus Team. This is just about how to write a plugin. We're not going to try to explain the details of how the Scribus plugin system works here. You don't have to know about them, but it'll help you follow what's going on better if you do. Issues like virtual and pure virtual functions, 'extern C' declarations, the details of memory management, etc are glossed over and avoided in this document. Some familiarity with Qt - mainly QString and QObject - will also help. You're assumed to know what a header file is, how include files work, know about classes an inheritance, and have some general familiarity with the language. This document assumes some basic knowledge of C++.

They are useful for adding extra tools, extra import and export functions, and for various more advanced uses. Plugins can extend and to an extent modify the behavior of the application without having to edit and recompile the core application. Plugins are libraries that are loaded into the main application at run-time. This article shows you how to write plugins for Scribus.

1.5.3 Storing your plugin's preferences:.1.5 Building plugins outside the Scribus tree.

Scribus 1.6