Apache OpenOffice (AOO) Bugzilla – Issue 52357
SDK: "Advanced UNO" chapter obsolete
Last modified: 2013-02-24 21:07:24 UTC
The Developer's Guides' chapter "Advanced UNO" presents the current state of language enviroments already implemented into the UNO model. The problem is, that it's not *current* and rather outdated. For example Python has already been developed and one can deploy UNO components with Python as well.
changing title since there is more than just the table that needs an update to 2.0 state in this chapter.
The probelm is that the Developer's Guide comes from Sun and Python is currently no official language binding (at least not for SO) and we haven't the resources to create a complete chapter for Pythoin for the Devguide. So as long as nobody else will create a complete chapter describing the Python language binding we will have this gap in the guide. But i will check the docu that Python is at least named anywhere and pointed to the description on udk.openoffice.org NEEDS HELP!!!.
tagging this issue.. Anybody feel free to jump right in!
There is more than chapter 5 - Advanced Uno to be updated : Python should also be documented at several places of chapter 18 - Scripting Framework. Currently, the Developer's Guide looks as if the authors were trying to hide the existence of python scripting and promoting java-like languages instead.
When the DevGuide was created a Python binding didn't exist. If somebody will provide this information we will integrate it in the Devguide otherwise it will be still missing in the guide.. Sun will do a review of this chapter and will integrate in the guide but not more.
later, when maybe an chapter for Python will be available
http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html Make a contribution We would like to invite you to participate in this effort, so as to cover the needs of the community and to bring in the community's experience. Please let us know what you would expect from the Developer's Guide, what might be missing in the current version, which use cases the guide should cover and which extensions you can think of. Please use one of the following ways to give us your feedback: Open a new issue if you want to contribute an article, sample code or if you find bugs in the guide. Component: api Subcomponent: documentation Issue type: ENHANCEMENT Assigned to: jsc@openoffice.org Note: You have to sign in and log on before you can enter a new issue. Mail to the dev@api.openoffice.org mailing list, using the subject: Developers Guide Note: You have to subscribe to the mailing list before you can post. How can I contribute something to this guide? We have currently not defined the best way how to integrate your contributions. But we think about a feasible way how you can easily contribute new examples and/or new chapters. Examples are always a good starting point for somebody who is searching for solutions and we should try to create a big collection of examples which covers all different application areas of the API.
i am not sure for what the last comment is good for. Anyway i will close this issue because i don't see a Python chapter in the near future. We plan to open source the guide in the wiki later this year (evaluation ongoing) and maybe somebody will prepare an appropriate chapter then.