[scribus-dev] Add-In Development Documentation

[Rob Oakes]

On 1/27/2012 8:36 PM, Owen wrote:
> With regard to scripting queries, have you perused;
>
> Help->Manual->For Developers
>
> If you get stuck trying to understand the API, have a look at some of
> the examples in http://wiki.scribus.net/canvas/Category:Scripts
>
> All the html for the help, Help->Manual->Documentation, is in the
> share directory, share/doc/scribus/en/ of your Scribus installation
>
> As for render frames, see Help->Manual->Documentation->Scribus
> basics->Working with Render frames
>
> I also draw your attention to Help->manual->other
> information->Documentation Copyright
>
> Wish you well with the project, with the plethora of iPhones, tablets, eBook readers as well as mundane monitors, I often think the way to go is HTML5 + css(3?)
>
> Sorry if you knew all this in the first place.
Thanks for the links and the suggestions. I gave the documentation a
cursory glance, but didn't dive into it nearly as deeply as I should
have. I've found the answers to many of my questions. The only one which
stumps me is how to get PyQt and extension scripts to behave on Windows.
(I haven't yet started to experiment on Mac OS X or on Linux, though
that's where I'm headed next.)

I tried the hello-qt example in the documentation, but was unable to get
it to work.  It gives an error when saying that the qt module doesn't
exist. I tried more traditional PyQt import statements and PySide
statements, but I wasn't able to get any of them to work. It looks as
though Scribus ships its own interpreter on Windows and I'm not sure how
to get it to interact with my system Python, PyQt, or PySide.

Do you know what the status of extension scripts on Windows is? I've got
a pretty good handle on how I need to structure everything else.

Cheers,

Rob