Removing C++ SDK examples, clearly encouraging Python extensions (was: LibreOffice prints on tuesdays)

[Olivier R.]

Hi *,


Bjoern Michaelsen wrote
> There is no dominant IDE (much less so a crossplatform one) and there
> seems to
> be a lot flux on which IDE is the en vouge one each year. Thus aiming to
> have
> simple, stable and robust build environment that is generic and
> independant is
> key -- whatever is the IDE du jour should be able to integrate that
> easily.

Adding examples of extensions in Python is a really good idea, as those who
like this language have almost nothing to learn how to begin with LO. There
is examples on forums, wikis or websites, but it’s sometimes obsolete or
confusing.

But, what is missing the most for programming LO with Python is good error
reports. You already have this on Linux, but on Windows, there is nothing
like this. By default, we are blind.

There is no error report if Python crash while running.
There is no error report if there is a syntax error (except when installing
extension, but not if you modify the code directly in extension folder).
There is no stdout for the command “print”.

Debugging on Windows is painful.

It’s possible to do some workaround with:

    if sys.platform.startswith('win'):
        import codecs
        sys.stdout = codecs.open("stdout.txt", "w", "utf-8")

and with:

        print(s)
        sys.stdout.flush()

Better than nothing, but LO/Python programming on Windows is still
difficult.

So, if we could simply have a window where LO/Python reports all encountered
errors and where to display what we want with “print”, that would be a
tremendous improvement.

Regards,
Olivier





--
View this message in context: http://nabble.documentfoundation.org/LibreOffice-prints-on-tuesdays-tp4047259p4049515.html
Sent from the Dev mailing list archive at Nabble.com.