On Wed, 19 Apr 2006 13:34:14 -0400, Marten Feldtmann <[EMAIL PROTECTED]> wrote:

Jürgen Schmidt schrieb:


The biggest problems with the current API are missing examples, documentation and maybe tools support. When you compare our API with the MS API you will see that our API is not so bad ;-). But for MS you can find thousands of books, examples and you have great tools/IDE support making the development easier.

 Make the BASIC IDE much better and more intelligent, then software
will come. The software model is (from the view of the IT concept) ok,
but for users .... no.


 Marten


I agree with Jurgen statement however the API newsletter is constanstly asking for new contributors for documentation. The issue here is a technical gap, if I have time to build documentation but lack the knowledge to build it, I cant contribute. And if I am a developer usually I am too busy to mind about documentation.

Yes snippets of code, a deframented developer guide and more blogging about the code that is being currently develop might make this easier for someone who want to document. Andrew Pitonyak for example has done an incredible job documenting the Macros / Basic framework. So has Ian Laurenson and Laurent Gogard. David on the other side has builded good resources regarding the XML schema of OpenDocument and how to hack it including perl snippets and XSLT.

However the API has not been so thoroughly documented (at least that I am aware of) and some things get just acumulated on the developer guide which really needs to be better supported. AFAIK the novell guys have documented a bit more and had ported all the docuemntation to the wiki. However most of this documents dwell more on the building process.

A feature that might make IDE better is integrated to Xray or PyXray on a way that can autocomplete the methods however basic itself is limited within the UNO framework. Java and C++ is the way to go to true hack the UNO space, this makes it a bit away from their range for the Basic IDE since is not made to handle java or C++ code. Cedric was working on a eclipse module but I am not sure if it was specifically for UNO developemnt.

Finally the place to really get all this information and documentation is on discussion form at the OOoForum and this mailing list where there has been some technical discussions about the API, IDL and the rest.

--
Alexandro Colorado
CoLeader of OpenOffice.org ES
http://es.openoffice.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to