Larry Gusaas <larry.gusaas <at> gmail.com> writes:
When will LibreOffice add support for using the Versions,
Full-Screen mode, and Resume features in Mac OS X version 10.7 Lion ?
When somebody writes the code. (And offers it for inclusion under the
license(s) we use.)
NeoOffice already supports these features in NeoOffice 3.2.1 Beta.
Which probably means that many volunteer developers who might have the
required skills and hardware have little interest in working on these
features as it would be duplication of work because of licensing
differences. Duplicating work just because of licensing is not fun.
At least that is how I feel...
(NeoOffice is GPL, LibreOffice is LGPL, and new LibreOffice code is also MPL.)
I did some inital experimentation with full-screen mode, and indeed,
supporting that to some extent is trivial. But exactly how Lion
full-screen mode should interact with/supplement/replace the
traditional OOo/LO full-screen mode, if at all, would be something
for the user experience experts to work on.
Versioning, Auto-Save, Resume etc would require quite a lot of work,
I think. The OOo/LO code does not use the NSDocument class at all,
for instance. (In general, the OOo/LO MacOSX code is rather old-fashioned
in its use of MacOSX APIs.)
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: 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