On Wed, 2006-06-12 at 11:35 +0100, Laurent Godard wrote: > OOo as a 1200+ pages reference document and an active community around > the api (with snippets site aso). it is wrong to say that it is poorly > documented
Ah, but it is... The _problem_ is that you have to read through 1200+ pages to get your head around the API. Good documentation is not the same as _long_ documentation. In fact, long documentation is very rarely good. Good documentation shows the user how to do something in a way that is clear, understandable and doesn't require an excessive time investment from the reader. I did try to read through the OOo API documentation. But it was far too difficult and complex, and I've heard the same comment from the other developers who want to use OOo as a platform. Short and readable tutorials would be better. But personally I see that difficult until someone first writes a simpler layer between UNO and the developer. The fact that the current documentation is 1200+ pages mostly reflects the fact that UNO _is_ complicated. > > If anyone is interested in doing this, I can put you in touch with some > > outside developers who currently use OOo as a development platform, or > > would like to do so in the future. > > And why not suggesting them joining the community, at Extensions project > if their willing to help and contribute ? I'm not too familiar with the Extensions project. What does it have to offer a developer who wants to use OOo as a development platform? I just stated that what they would like to have (AFAIK) is a simpler API and documentation that is easier to read and understand. Judging only from the name, it looks like this is a project about making extensions for OOo, so it is not clear to me how it relates to what I said before. Best, Daniel. -- "I AM in shape. Round IS a shape."
signature.asc
Description: This is a digitally signed message part
