Daniel Carrera wrote: > Mathias Bauer wrote: >> (2) The completeness of the API doesn't depend on the programmming >> language. I think you wanted to express something different. Could you >> please elaborate? > > No, what I meant is that, last time I checked, PyUNO didn't implement > the entire API. Or at least, that's what I heard.
PyUNO doesn't implement any API, it just provides a binding to access it. That's a big difference. Perhaps you mean that pyuno doesn't support all API elements, but IMHO it supports even more elements than OOo Basic (if not everything). As an example, you can't deal with exceptions in Basic and you can't implement objects with it (not really at least). Both is possible with pyuno. I don't know anything you can do in OOo Basic but not in pyuno. >> If you compare OOo to MSO: I doubt that the OOo API is much harder to >> learn, maybe harder to start diving in. > > I don't know MSO, so I can't say. But I thought other people had said > that the OOo API was much more difficult because it was more granular. > So, on the one hand it gives you more power, but on the other, it's a > lot harder to learn and use. That's what I mean: it could be harder at the start, but any serious user that works with the API more than just a few days shouldn't have more problems with the OOo API than with the MSO API. The problem is the start, we need more documentation to make it easier. Hopefully the new developer documentation contest helps us to make a step forward. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
