Aqua OpenOffice.org v2.0 Cancelled
Ant writes "According to MacSlash's story, a recent post on OpenOffice.org said no Mac OS X work has been done since 2003 and that there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :("
I think it's not all that easy to install OpenOffice.org as X11 application.
It requires some work (according to what I heard).
In other words: it won't be popular for 'Joe Average'.
Join the anonymous, help develop the network: http://www.i2p2.de
Yeah, I run OO under X11 on OS X - but it is as ugly as it is on Linux. Which is pretty damned ugly and slow.
...And when they came for me, there was no one left to speak out for me." - Martin Niemoeller (1892-1984)
It's disappointing news, but at least there's still the NeoOffice project. Its was originally intended to be a place for experimenting with the issues involved in a native OS X port, but if the office OOo project won't be doing it hopefully NeoOffice will get more support as the primary (er, only) Aqua version.
Except for that in the first paragraph of the article it says that a port is being released by NeoOffice. Did anyone even rtfa?
The non-aqua version which uses the X server works fine... if your objective is to have something that works similar to Linux.
It works fine until you actually want to use the wealth of rich, high-quality fonts that comes with OS X. So I guess that makes the NeoOffice/J project ever more important.
The NeoOffice/J team has done a fantastic job of gradually Aquafying OpenOffice without anywhere near the same resources.
Regardless of the progress on native porting (or lack thereof), continued X11 development is crucial for the ongoing viability of OpenOffice.org on Mac OS X. There are a number of critical factors that make X11 more relevant then native porting:
X11 Will Always be Faster to Market.....
X11 Will Always be More Stable.....
X11 Will Always Look like Other Platforms.....
X11 is the Ultimate Testing Tool.....
So essentially, what they're saying is, X is their basic graphical platform, they want it to stay that way, and they don't want to divert efforts to do a native port for a machine that they consider a niche market.
They're just focusing on what they think will make the most users happy. Simple as that.
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
Functionally, there is little difference except that is certainly slower than running it natively. Where the big problem lies is that Mac users (and I'm one of them) expect coherence and integration in their UI. A Mac version of OpenOffice that runs using X11 will not provide this.
Also, think of anyone who's switched over from Windows with a sour taste in their mouth - they want to avoid Microsoft at all costs, including MS Office. They've heard great things about OpenOffice, but when they go to try it, it's slow and kludgy. Not a very good impression at all.
Other than being free, I don't see what OpenOffice has to offer on the OS X platform. KeyNote works great, version 2.0 looks even better, and for those who care (and I'm one of them), the file format is xml-based and completely transparent. The OS X paradigm of encapsulating applications and documents in a directory instead of some gigantic kludgy single file means you can go into a .key file and see all the images and movies you've added to the presentation, as well as a single "presentation.apxl" file that contains the presentation itself in a completely obvious xml format.
.edu discount.
The new word processing program for the Mac announced at this year's MacWorld, called Pages, was written by the same team that wrote KeyNote and presumably uses the same open file formats.
And these programs together are $79; even less if you can get the
There's no Apple spreadsheet program (yet)...
Ant writes "According to MacSlash's story, a recent post on OpenOffice.org said no MacOS X work has been done since 2003 and that there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :("
It says nothing of the kind. From the link:
Due to various licensing, political, and fundamental engineering difficulties it is likely, for the near future, that native Aqua porting work will be based off of the NeoOffice.org project and not under the direct aegis of OpenOffice.org.
and
For the last year and a half all engineering work focusing on a native Mac OS X OpenOffice.org version has been concentrated in the NeoOffice/J project, using a combination of Java and Carbon technologies to replace X11.
What it looks like is that they have recognised that NEOoffice is a valid port, and any Aqua port by themselves would be a duplication of effort. The Slashdot story blurb makes it sound like they just gave up because it was too hard. They call this journalism now?
It just doesn't work very well. It's interface runs slowly (on my 1Ghz G4 Powerbook) and it doesn't fit in well with the rest of the operating system. Also the Powerpoint clone doesn't actually work properly as I was unable to get it to run the slideshow full screen, which makes it effectively useless for anything other than composing presentations.
I use OpenOffice all the time on Linux, but for my Mac I went out and bought MS Office as I needed Office software. OpenOffice on X11 just doesn't work well enough for it to be any use.
http://www.ragtime-online.com/ it beats Openoffice hands down. just my ,02
Ignorance forgiven :).
Mac OS X Panther (10.3) does indeed come with an X11 server. However, there are two caveats to this:
Not a major problem for power users who need X11 support (this was virtually the first thing I did when I took posession of my first PowerBook last year), but hardly something you can expect your average user to do.
Yes, there are multitudes of such problems, including:
That's just a sampling of issues off the top of my head.
The one thing they did at least do was to integrate OOo with OS X's clipboard support directly, making cut and paste between applications work as expected. But that appears to be the extent of OS X support.
I'm rather disappointed in the attitude of OOo in this regard, because OS X really should have a native port of OpenOffice. The only way OpenOffice can take on Microsoft is to not only build a better office suite, but to make sure it's available virtually everywhere in versions that integrate well with whatever operating system it's being used on.
Anyone other than me remember when StarOffice's target operating system was IBM's OS/2?
Yaz.
I looked at OOo with the thought of helping out with the native port, but recoiled when I actually looked at ths sheer size and complexity and skill necessary. Another important point in the linked post is that moving to Aqua will take "a couple thousand hours of developer time," which I actually think is being optimistic. Unless an experienced somebody or, more likely, team of sombodies is willing to put their nose to the project 40 hours a week, like it's a full time job, it's not going to happen. And even if it does happen, it will break compatibility with the rest of OOo.
OOo, I'm sorry to see you go. At this point it might be easier to start from AbiWord and move out to develop a full office suite on the Mac. The tension between being "Mac-like" and coordination with the rest of OOo -- which isn't anywhere near as mature as MSO, yet, anyway -- is too great.
First of all, we have some nice, juicy, out of context quotes like this one:
no MacOS X work has been done since 2003
when in fact the page linked to states:
all engineering for OpenOffice.org Mac OS X has been focused on X11 graphics, that is, OpenOffice.org Mac OS X (X11).
Then, faithful Slashdot reader, we are informed that: there are no longer any plans for an Aqua version 'due to various licensing, political, and fundamental engineering difficulties'. :(
When in fact, although there will not be an official OOo in Aqua, there is this:
For the last year and a half all engineering work focusing on a native Mac OS X OpenOffice.org version has been concentrated in the NeoOffice/J project, using a combination of Java and Carbon technologies to replace X11.
So you can just use NeoOffice/J
So basically what we have are a group of developers not willing to take the time and effort to go headlong into learning a specific OS's nuances and tweaks, and majority reworking the code to run natively in OS X, but who will keep making an X11 version that keeps up with the other platforms, and there is a 2nd set of developers working that into a native port. Doesn't seem like the end of the world to me.
So have no fear, OOo is here to stay on OS X, and NeoOffice/J is here to work on a native port.
e to the pi i plus one equals zero
One problem with this is that X11 is not installed by default in Panther. You have to choose "Customize" and then click on X11. As most people don't know what it is for, most will not install it. This, more than perhaps anything else, is a hurdle for basic Mac users.
I really was hoping for an Aqua port that worked well. X11 is just a bit of a pain for those who thrive on Apple's consistent UI.
iWork looks nice (I played with it more than a bit at MacWorld this week), but I would prefer OO in Aqua (Pages, to me, seems more of a page layout tool than simple text editor that replaces Word).
In short, there's still plenty of options (even TextEdit is a fine basic editor), but I had really been hoping this would come through. Let's hope that things may change and a port comes through in the next few years.
http://www.apple.com/opensource/
How do you like the contributions to KHTML that Apple provided? What about the PPC additions to GCC?
They are fully compliant with the licenses of the software they use and modify. Did they have to give the Streaming Server to Open Source? No. Did they have to open source Rendezvous? No.
Jesus was a compassionate social conservative who called individuals to sin no more.
I guess everybody's just too busy constantly recompiling their Linux packages from source to mess with an OS X port.
Why would Linux users care one iota about an OS they don't use??? Do you contribute time and effort into Linux projects?
"What's the frequency Kenneth?"
See some of the earlier posts, but in general:
It's a hassle to use X11 under Mac because you must start up X11 and then OOo. Additionally, the menus do not behave as other Mac menus do, and the integration to the rest of the desktop isn't perfect.
Aqua is the name for the most current display widgets for Mac OS X. Quartz is the video display technology they're built upon. A native Aqua/Quartz application uses the Mac OS X desktop natively, without going through an X11 server that sits as an intermediate.
Firstly the anouncement is purely for the Version 2.0 codeline. This is an excellent idea because it focusses everyones attention on getting the best Mac Port possible in the timeframe, not scattering resources trying many things.
The Mac effort is one of the most intense efforts in OOo today by FOSS developers. There are many volunteers and almost daily offers for additional help. So as they say, news of my (OOo) death is premature.
Ultimately the NEO office port will be merged with the mainline OOo. At this stage there are some issues with doing this cleanly so it is managed (extremely well) by a third party. This will continue until the whole thing becomes clean enough to merge. Try NEO if that works for you that is still a win for OOo in my book, I do not care about the brand name frankly my effort in making OOo better in a number of small ways is paying off, I am proud.
Finally do not forget that this is an Open Source development. Any predictions that something will not happen are just very unlikely because someone with a bee in his or her bonnet will do what you do not expect. If you want an Aqua port more you want a serious stable Office Suite using X on Mac then please by all means, do that.
I've got a Qt app I distribute for Mac. It looks native because it *IS* native. It uses the native Qt/Aqua. The widgets are genuine Aqua widgets because Qt uses Aqua to draw them. The menu bar is placed at the top of the screen. The configuration menu was moved as appropriate. Etc, etc, etc. With a few carefully placed #ifdefs and a properly constructed icon and application bundle, no one can tell it's really developed under FreeBSD.
Don't blame me, I didn't vote for either of them!
Moreover X11 is an optional item (default=no) when you initially install the OS. My guess would be that the large majority of Mac users don't have it installed.
Just because the didn't pick your pet horse...
It's kinda like expecting really good support from Apple for Mozilla when they'd rather push Safari
You do know that Safari is built using KHTML & KJS (both part of KDE) and Apple is supporting them by feeding back bug fixes, enhancements and optimizations.
Also they have made those frameworks available to other developers, outside of Safari, on Mac OS X by bundling them with the OS distribution.
WebCore