We could use some good documentation on how to work with Python and LibreOffice. This could be done with a wide range of means: - add examples to https://gerrit.libreoffice.org/gitweb?p=sdk-examples.git;a=tree - write accompanying prosa on https://wiki.documentfoundation.org/Macros - create Youtube Videos a la http://www.youtube.com/watch?v=2gIqOOajdYQ&hd=1 Get creative!
adding LibreOffice developer list as CC to unresolved EasyHacks for better visibility. see e.g. http://nabble.documentfoundation.org/minutes-of-ESC-call-td4076214.html for details
Björn, I will take this bug, and write some examples using PyUNO. Is there something else that I can do with Python?
(In reply to comment #2) > I will take this bug, and write some examples using PyUNO. Could you change the status to ASSIGNED as you're owner of this bug now? Thanks.
OK.
Björn, I've made a patch. How can I push to the sdk-examples repo?
(In reply to comment #5) > Björn, > > I've made a patch. How can I push to the sdk-examples repo? Forget. :)
Putting this back to new -- there ~never can be enough documentation and multiple people can work on this.
Some changes pushed as: https://gerrit.libreoffice.org/gitweb?p=sdk-examples.git;a=commit;h=9ebc815e7af4d6c9ddf05769df3e6332886399ae https://gerrit.libreoffice.org/gitweb?p=sdk-examples.git;a=commit;h=1b0756166a92c4fcc4d98b2fcc9c3d02532f147f
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner SkillPython) [NinjaEdit]
JanI is default CC for Easy Hacks (Add Jan; remove LibreOffice Dev List from CC) [NinjaEdit]
Is there someone who can work on this bug/missing_feature ? If not, maybe, I can do some contributions to this. I'm not sure where to start because I've recently found out about LibreOffice. Some of my background, I've been working in VBA for some time now and now I've recently discovered Apache OpenOffice. At the beggining I didn't understood why this OpenOffice uses this obsolete, hard to write, VBA stuff, because other languages have major advantages over this. I've been just scratch the surface with python in OpenOffice. After that some of my work coleagues use LibreOffice and showed me that LibreOffice vs Apache OpenOffice seems more up-to-date with what end-users need. Also Apache OpenOffice is <3 where LibreOffice is >3. The fact that there not easy-to-use documentation of how to use python with LibreOffice make people not so easy to get involved this stuff. Maybe I can help, with some documentation, maybe some examples. ( I've only recently findout how to embed python scripts inside the actual .odt document, but you have the edit the manifest.xml, and thats not very user friendly, also in order to edit a python script inside the .odf file, you need to have some tricks in place, because LibreOffice does not support editing files except basic ? )
It is. not assigned, so feel free to assign it and work on it,
Assigning to myself. Any tips on where to start as this is my first open source contribution.
(In reply to abdulghzain from comment #13) > Assigning to myself. Any tips on where to start as this is my first open > source contribution. In order to write a pyUNO tutorial, you need to play with the API, and look in our wiki for information: https://wiki.documentfoundation.org/Development/PyUno (most of this documentation is from the good old OO days).
A polite ping still working on this issue ?
Hi JanI, I am assigning this bug to myself and would be working parallel without changing the Assignee.
A polite ping, still working on this bug
A polite ping, still working on this bug?
some identified Python libO content: https://wiki.documentfoundation.org/Macros/Python_Design_Guide (wip) https://help.libreoffice.org/6.3/en-US/text/sbasic/python/main0000.html
Closing since PyUNO documentation has been greatly improved in the Help (Thanks to LibreOfficiant)