Roberto Battistoni wrote:
Ok, but how far is this future?

OpenOffice is a great editor, but its SDK with API and UNO framework is
too complex as compare to Winword environment with .NET and C#.

I like OpenOffice, but productivity is an important factor for
enterprises that want to invest in OpenOffice.

of course your are right productivity is important and as Stephan pointed out we are working on improvements. But changing existing APIs will probably take longer because the pure functionality is already available. We have to find a compromise between new features, new APIs and adapting existing API areas. We will first adapt often used APIs (document APIs) and will go deeper to other APIs. We will also define some high level APIs for often used functions but we will definitely not create any language specific wrapper. Our approach is to make use of the "UNO ease of use" features to make APIs more intuitive and easier in the future. This has the advantage that all language bindings will benefit from this improvements.

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.

Cedric is working in an Eclipse plugin, we are working on a NetBeans integration and other tool support will probably coming as well.

Juergen


Thanks all
Our vision of the future is that the OOo UNO API will improve so much (using multiple-inheritance interfaces and new-style services, and offering high-level APIs) that developers will feel no need for a wrapper for the UNO Java language binding. ;)

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


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

Reply via email to