Laurent Godard wrote:
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
you misunderstand me, this info shouldn't be part of the DevGuide, it
was intended more for me because i will probably integrate it in the
SDK. And if possible the reference should be build automatically during
the build like the Java, C++ and IDL reference.
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
you mix again two things. The SDK is totally free and open source. Only
the DevGuide is a Sun document which of course is made available for
free as well and which is part of the free available SDK.
What documentation would be available if the DevGuide wouldn't be exist?
Ask yourself how many answers do you have got form the guide and others
as well for their own books or to answer simply questions on the mailing
lists. You should keep in ind that Sun is not the "bad guy" who simply
takes everything from OpenOffice.
Sun offers simply to maintain the guide professional and make it
available for free.
Ok it would be nice if the guide would be open source but Sun has
decided to provide it under a special Sun documentation license. Maybe
this will change in the future, i don't know. But fact is that until
today nobody has tried to contribute a bigger part to the DevGuide and
so we don't have had any problems so far.
Juergen
Let us know
Laurent
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
