Apache OpenOffice (AOO) Bugzilla – Issue 54951
Include Python UNO Runtime Reference into SDK docs
Last modified: 2017-05-20 09:32:10 UTC
There are some steps to do here, the first is already done (doc-strings) but would need a check for some obvious grammatical/typo mistakes. The second is generating the html files with pydoc and the third is to apply css style that is common in the sdk docs (see C++ UNO Runtime Reference, Java UNO Runtime Reference) to it. Final step would then be to make it fit into the build process. cyb->jsc: Please give some input whether you would like to have it included into the sdk docs, in my opinion it would fit quite well under Java UNO Runtime Reference. The only difficulty I see is that PyUNO is an optional installation package and not installed by default, as far as I know - but I am not sure what the newest state of things is.
adding myself as CC
Under the Java reference is probaby the correct place. But before we can integrate it somebody have to ensure that pydoc and everything else is available in the build process because the docu for the SDK is generated during the build process automatically. After that i would integrate it in the SDK. But of course i would like to have a language bindung chapter for the DevGuide as well. Otherwise the binding is incomplete for me.
i think that i am not the right owner for this issue or let us say for the pre condition. First somebody should provide a DevGuide chapter deacribing the language binding, second somebody should create the reference documentation in a way that it fits into the SDK and then this issue can come back to me and i will integrate it in the SDK.
adapt target, it seems that nobody feel responsible for the pre condition to provide the reference in a suitable format for integration.
later, when maybe an Python chapter will be available