Slashdot Mirror


OpenOffice 2.0 Preview Release

gmuslera writes "A preview release of OpenOffice.org 2.0 was released, which has new features like better MS-Office compatibility, an Access-like program and a more. Here is a review of it with screenshots and how it performs. It's work in progress, maybe not recomended for production sites, but it is a good sample of what is coming."

1 of 517 comments (clear)

  1. Not anytime soon from OOo...look at NeoOffice by soullessbastard · · Score: 5, Informative

    Disclaimer: I am one of the community members of the Mac OS X OOo "team" and founder of the NeoOffice project

    It will probably be a while before you can even see X11 support for 2.0. Eric just got the 2.0 X11 based code to *compile* for the first time yesterday and it won't even run as setup crashes.

    Part of the problem is that OpenOffice.org really isn't a "team"...it's primarily Sun Microsystems. Sun has four priorities: Linux x86, Windows, Solaris, and Solaris x86. Sun pays no one to work on Mac OS X support. Since it isn't one of their priorities, they frequently code without keeping the special needs of Mac OS X in mind, doing stupid things like hard-coding shared library extensions to only be ".dll" or ".so", neither of which are used by Mac OS X. They can't claim ignorance since folks have been trying to write Mac OS X code for over three years now, but yet they still don't even keep simple compatibility needs like that in mind.

    Getting true native support for OOo without X11 on Mac OS X is most likely not going to happen within the OpenOffice.org project. All of our native work has been going on in the NeoOffice/J project. It uses a mixture of Carbon and Java to run using ATSUI for native fonts and Quartz for native drawing and printing. We also use full GPL licensing so we can incorporate the good work of contributors who can't get their translations and patches into OOo due to licensing and politics.

    The process of giving it Aqua widgets has already begun. The latest 1.1 Alpha patches use native Mac OS X menubars. Aquafication is slow, though, because our first priority is to make it functional first, then make it pretty second. It doesn't matter if it looks pretty if it crashes after 5 minutes!

    For what it's worth, it's already taken over two years just to get NeoOffice/J to the point where the native Mac OS X support is functional. By functional I mean that it can copy and paste both formatted text and images with other Mac OS X applications, has correct fonts and font layouts, functions with most all of the Mac OS X printer drivers, launches properly from the finder, works with the scrollwheel on those funky mice some Mac users have, has an integrated WordPerfect filter, uses the Apple Installer, has automatic upgrade notification, automatically translates the interface based upon your preferred language in the System Preferences language pane, etc.

    OpenOffice.org 2.0 X11 has no native non-X11 support in it, much less the level of integration with Mac that we've achieved with NeoOffice/J. It's taken two years of some really dedicated engineers (namely, Patrick) to get NeoJ up to that stage. Replicating all of that work within OOo will probably take nearly that long and perhaps longer if the experts aren't there to help.

    NeoOffice/J is in fact OpenOffice.org 1.1.2, and is 97% identical on a source code level. It's even got bug fixes that aren't in the OOo GM (such as functional JDBC support). This week we're going to be taking NeoOffice/J to 1.1 Beta after all known crashing and deadlocks have been fixed. And...

    NeoOffice/J 1.1 Beta will be based off of OpenOffice.org 1.1.3, which isn't even available for Mac OS X X11!

    Just keep up to date on the latest Mac OS X porting news on trinity instead of the infrequently updated OOo pages. RSS feeds are available too.

    And don't let all of the politics and scare tactics of the OpenOffice.org denziens scare you either. NeoOffice really is the 'official' place for Mac OS X native OpenOffice.org and is where all of us core developers work (Patrick, Dan, and Ed).

    ed