Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


Howdy Tom,

Well, I was specifically asking Mauricio, after looking over the example
basic code particularly, I am interested in his thoughts.

As for this being the user mailing list, macros are user level question I
would think, Basic is assumed usually, but Python is just as valid and
about as easily done these only to drop in a couple of extensions.  Maybe
it is a power user question, but still a user question, yes?

However, I suppose your'e right when moving on to talking about generating
extension packages from macros libraries (basic or python).

Thanks

On Sun, Jul 8, 2018 at 3:50 PM Tom Davies <tomcecf@gmail.com> wrote:

Hi :)
I think the Devs Mailing list or IPA, IIRC or whatever is prolly better at
giving a good answer to that.  They may be annoyed as it's prolly not what
they usually post to there.  Maybe it's best to try the QA Team?

There used to be a "mentoring" program to help people start to code for
LibreOffice.

I think LibreOffice is mainly Python but with significant chunks of C, C++
and C# and smaller amounts of other code.  I think pretty much all the Java
has been over-written in Python now.

There may be some devs on this mailinglist who can answer you but it
doesn't hurt to have other places to ask too.  Actually i thought you were
one of our devs but there we go.  I know you have done a lot for LO.
Good luck and regards from
a Tom :)




On 8 July 2018 at 20:30, Drew Jensen <drewjensen.inbox@gmail.com> wrote:

Howdy, Mauricio, Patrick

I am curious as to why you think python is always the better choice? (ie.
error handling, or whatever; or is it just always so in Patrick's use case
and the example code you supplied there)

Also, I you don't mind me asking. I'm new python scripting in LibreOffice.

Do you have recommendations for setting up tools with LibreOffice to with
Python scripts and perhaps then turning those into an extension.

Right now I am using the following: LibreOffice 6.x, APSO (latest), MRI
(latest), MS Video Code. Which of those would, if any, would you suggest I
look at replacing.

Thanks and best wishes,


On Sun, Jul 8, 2018 at 3:13 PM Mauricio Baeza Servin <elmau@amigos.email>
wrote:

On Sun, 8 Jul 2018 21:03:02 +0200, Patrick Gelin <patrick.gelin@free.fr

wrote:

Ok, with a factory for self variable into pseudo objects. I was
thinking
of this solution already, but I was hoping a better solution in next
version ...
- Do you need this pseudo object code could be better object model
complient next day ?
- Or do you think python will be a better way for
OpenOffice/LibreOffice
futur ?



Of course, definitely, Python is much better, I always recommend; learn
and used Python with LibreOffice


Best regards
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more:
https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy


--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems?
https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy




-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.