Hello everyone,
I found out in LWN (http://lwn.net/Articles/414051/) that the LO team
was working on "The crufty old virtual object system - deprecated for
ten years - is being removed."
From what I understand, that means revamping the API for developers. Am
I right?
I have a requirement to integrate my solution with OO. Frankly, I'd
rather go for LO because a) LO is truer open source b) LO is (in my
opinion) going to be the de-facto standard ODF editor suite in the
future and c) OO's API are a pain to even _look_ at.
This article is a month old. So, I wanted to know how far ahead in this
revamping effort we are, and how much more work is needed until we have
a stable API to code with.
Thanks and regards,
--
Marc-André Laverdière
Software Security Scientist
Innovation Labs, Tata Consultancy Services
Hyderabad, India
--
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***
Context
- [tdf-discuss] Revamping of OO APIs · Marc-André Laverdière
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.