Hi Daniel,
Daniel Carrera wrote:
Bernd Eilers wrote:
it is always a good idea to start by getting familar with
OOo´s component model UNO, therefor you should have a look at the OOo
Developers Guide, which can be found at the following location:
http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html
If I were Claudia, I'd read up to here, go see the developers guide and
hit a huge road block. This document is enormous and very very very hard
to understand. After trying to wrap my head around it for a few weeks
I'd decide that this is just too difficult and I'd then move on to the
Gnumeric list and ask if they need help.
I don't think that the Developers Guide is a good starting point for
prospect developers. It can be mentioned as a *reference* but not as a
"read this first" thing.
I agree that the Developers guide is not for non developers and that it
is probably hard to start with it. On the other side the guide provides
a first steps chapter which was introduced to give a smart start in the
whole material. We often asked for really good and fundamental feedback
but we hadn't got to much.
We need definitely more documentation based on top of the Developers
Guide like Andrew Pitonyak's Macro book (Andrew got a lot of info from
the Developers Guide). Documentation for the different languages and
different user groups (macro programmer, plugin developers (e.g.
add-ons, calc add-ins) are necessary. Core developers definitely have to
read the Developers Guide which of course needs to be improved and
updated frequently.
Feedback is always welcome but our resources are limited and we (the
core developers) can only provide this kind of base documentation and
can offer our help on the mailing lists. Authors who want to write books
in the area of programmability features of OO are welcome and i offer
again my help to provide the necessary input and i would do reviews if
desired.
It would be good to have a friendlier tutorial avaliable, and to review
i agree, short tutorials for only one special aspect (e.g. add-ons)
would be really helpful. But of course the Developers Guide was never
introduced as a tutorial.
the Developers Guide for readability. I never did manage to read the
whole thing. Or even a significant portion of it.
You are not a developer and you did not understand the guide, right? You
should see the guide as a book where some base programming skills are
necessary to understand the concepts described in the guide.
Juergen
Cheers,
Daniel.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
