Cool - thanks for clarification! :)
Malte.
On 19.07.2011 01:54, Rob Weir wrote:
On Thu, Jul 14, 2011 at 7:20 AM, Malte Timmermann
<[email protected]> wrote:
Hi Erik,
thanks for clarifications :)
Some questions below...
On 14.07.2011 05:09, Yong Lin Ma wrote:
...
We are willing to contribute the whole Symphony to community. The code
would be available to the community. (The C++ part of Symphony, also
the counterpart of OO.o in Symphony).
Maybe I misinterpret "The C++ part", but does it mean you will contribute
the changes that Symphony needs in the OOo code base, but not the Symphony
"Application" itself?
From what I know, the Application and all UI (the "chrome") is written in
Java, and just embeds the OOo applications. So not contributing the Java
part would mean that the "praised UI" that Rob mentioned wouldn't be part of
the contribution...
Hi Malte,
Sorry for the delay in responding. I've been traveling to and from
Berlin for the recent ODF Plugfest. I am just starting to catch up
with my email.
I'm attaching a screen shot of the Symphony UI that shows what parts
we're contributing. As you can see, the Symphony UI has four areas of
interest:
1) The outermost part, with the tabbed interface, is our customization
of Eclipse, which we call "Expeditor"
2) Embedded in that we have a document editor window, which is our
customized OOo
3) To the right of that is the properties panel. This is C++ code.
4) And to the right of that is the widget Panel, which is based on Eclipse.
A red rectangle is drawn around the part that we can contribute, in
C++ and without dragging along Eclipse as a dependency. I think this
is the key UI improvement. It is especially good on wide screen
monitors, since it makes good use of the available horizontal space.
By far, we should focus on getting the first Apache OpenOffice release
done.
Right! :)
3, A key performance improvement in Symphony is Async document loading for
Writer and Presentation documents. User can see document content get
displayed before the whole document content get loaded. It would be more
difficult to integrate this into Apache OpenOffice than other features
Symphony has
Isn't this a feature that's completely implemented in the OOo code base?
My assumption would be that this has no dependencies on Symphony related
code - but of course I am just guessing, as I don't see a reason why such
dependency should exist.
Last but not least I would like to add that it will be a pleasure for me to
continue working with your team on OOo! :)
Best regards,
Malte.
