Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On Jul 14, 2011, at 6:17 PM, plino wrote:

Surprise, surprise!

IBM will be announcing tomorrow that it’s donating essentially all its IBM
Lotus Symphony source code and resources to Apache’s OpenOffice project

I think Symphony has done a great job with its UI work--that's what I'd most like to see come under 
an open source license.
- tabbed document interface lets you open multiple files in one window
- a "dashboard" like the OOo / LibO splash screen, but you can open it from a button that appears 
on the tab bar. This fits into the dashboard functionality with potential integration into online 
services, as I have envisioned and previously described:
- formatting and other tools appear in a vertical column on the side of the main document window, 
which is one of the most-frequently requested UI features I've seen come through the OOo and LibO 

Symphony also has some problems:
- it's very slow to open the application initially
- removed the Draw component
- I think (?) it's even more Java-dependent than OOo ever was

Rob Weir's full email is available online here, and his official announcement is this afternoon in 
Berlin (so it could be happening right now or has just happened):


Benjamin Horst
646-464-2314 (Eastern)

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.