[scribus-dev] extensibility

[Craig Bradney]

On 1/13/10 10:14 PM, Alexandre Prokoudine wrote:
> On 1/13/10, Andreas Vox wrote:
>
>   
>>> Hi,
>>>
>>> It is probably a silly question, but from what I can see it's not
>>> quite obvious... Quite a bit of Scribus's functionality is implemented
>>> as plug-ins. Is it architecturally possible to create 3rd party
>>> plug-ins (not in Python) for Scribus?
>>>       
>> Not really. Scribus plugins depend heavily on the rest of the code, there is
>> no clean interface.
>>
>> I think we should rename those "plugins" to "modules" and define a clean
>> plugin interface for scripting.
>>     
> Um, just scripting? :)
>
> My point is... I'm looking at GIMP 3rd party plug-ins right now --
> GAP, Liquid Rescale, Save for Web and so on -- and I see that a lot of
> functionality (and GIMP GAP is quite large) can be written outside of
> core project, so I was wondering if it would make sense encouraging
> 3rd party development.
>
> For instance, GIMP has a plug-in template, so anyone can use it to
> create a new plug-in which will load and work nicely and UI/docs would
> be localizable. This is really helpful for creating vivid community
> around the core project.
>
> Alexandre
>   

see the myplugin in the plugins directory.. a template..

Craig