On Fri, 2012-07-20 at 17:20 +0200, Lubos Lunak wrote:
Now, if you look at
http://wiki.documentfoundation.org/Development/LibreOffice4 , a lot of the
stuff there does not belong to the page at all, as it has absolutely nothing
to do with any of the above:
Can you edit the page to separate the pieces that you don't believe
require ABI change from those that do ?
- "de-UNO-ize the ODF import and export filters." is a purely internal matter
that does not affect anything outside of LO core (or am I wrong here?)
that depends on whether crazy people have tried to hook into / use
those interfaces from their scripts etc. Anything exposed is scripting /
plugin-authors is liable to their random walk attacks of this nature :-)
Summary:
- it needs to be said what we expect from "LibreOffice4"
Very true; I've used it to refer to the ABI breakage we've been needing
for a long time to cleanup our accumulating cruft issues.
- the wiki page with technical tasks needs to be cleaned up
It'd be great if you could do that separation :-) please don't delete
anything though - some tasks are rather succinct but useful to retain.
- we need to decide how to deal with the fact that LO4 will break backwards
compatibility
Of course, we need some good technical ideas. In particular, I'd love
some stub / skel libraries and clever bridging with old names to rid us
of the com::sun::star evils ;-)
ATB,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
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.