Hi Juergen
thanks for your explanation
this is a huge work :-)
But yes a missing part
Some Python examples related to the chapters should be created and
should be part of the SDK (short description for the example overview
page). Ideally integrated in the SDK build env.
Yes !
Python UNO runtime reference documentation. Howe to build from scratch
during the build process if possible. HTML docu with a css to customize
the look and feel to look similar as the other available reference docu
would be also nice.
This is an other issue imho. Not dedicated to uno component creation
I may be wrong, but there is no information in the dev guide how to
build CLI uno support or even Java ;-)
But again, i may be wrong
License for the DevGguide is a good question. It's a Sun documentation
license and i don't know the details at the moment and can't say how
external contributions are handle or possible. But i will check it
because it should be possible to integrate community work easy.
Do not expect any contribution from the community (at least from myself)
until this is not clear and the SDK is not free. Final document licence
but also tools to build the final result have to be clearly stated as free
Let us know
Laurent
--
Laurent Godard <[EMAIL PROTECTED]> - Ingénierie OpenOffice.org
Indesko >> http://www.indesko.com
Nuxeo CPS >> http://www.nuxeo.com - http://www.cps-project.org
Livre "Programmation OpenOffice.org", Eyrolles 2004
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
