Sun Joins Mac Open Office Development 171
widhalmt writes "In a blog post, a developer at Sun Microsystems announces that Sun will help with porting Open Office to Mac OS X. The open source office suite is well known on Linux and Windows, but does not have a native version on Mac OS. For a long time Sun did not want to join the development of that port but now they will actively push it."
Re:Not true! NeoOffice! (Score:5, Insightful)
Re:Not true! NeoOffice! (Score:5, Insightful)
Given its heavy use of Java I think the 'native' qualification is debatable. Some aspects are native (e.g. font management), which is certainly a major plus.
Unfortunately, though, this application gives new meaning to the words 'slow' and 'bloated'. The author has also chosen to make its license (GPL) incompatible with OO.o's (LGPL) so that his porting efforts cannot be contributed back to the main project. That makes NeoOffice a very hostile fork. What's more, he is trying (against the terms of the GPL/LGPL) to limit free distribution [neooffice.org] by using the trademark loophole.
So, I would say that while a port exists, it's both low quality and under bad management, and I welcome this new effort to do it properly.
Re:NeoOffice is not 'native' in a sense... (Score:5, Insightful)
I hope you appreciate the irony of that statement.
Re:Not true! NeoOffice! (Score:3, Insightful)
Re:Not true! NeoOffice! (Score:2, Insightful)
Re:OO has been on OS X since 10.0 (Score:3, Insightful)
Re:Not true! NeoOffice! (Score:5, Insightful)
I must be doing something wrong, since my NeoOffice (2.1 patch 3) takes about 10 seconds to start.
Re:OO has been on OS X since 10.0 (Score:3, Insightful)
Exciting! Can't Wait! (Score:5, Insightful)
So I say, bring it on! I think that getting a good implementation of OOo running natively under Aqua is key in the cause of reducing reliance on Microsoft. People switching to Linux obviously are going to use OOo or some other open format, but still too many people switching to Mac are relying on Microsoft. It'll be curious to see whether they take Firefox's approach to have the interface be consistent across the board, or if they try and take advantage of OS X's toolkits and design guides to make it a true Mac application.
Re:Port it all you want... (Score:4, Insightful)
- Keeping an informal "database" of crap in Excel or Calc - Both will sort the list by whatever column your highlighted cell is in if you hit one of the "A->Z" or "Z->A" buttons. But Calc will treat the column headings as data and sort them into the middle of the list! Excel knows that the first line is not data if it's a different text style from the rest of the list. Polish.
- Printing in Excel or Calc - Having a sheet loaded and trying to print will print the whole entire freaking spreadsheet, all sheets, all ranges in Calc. That's just stupid. Excel will (for obvious reasons) default to printing only the sheet you're on. More polish.
- Mail merging in Word or Writer - Trying to get Writer to realize that "mail merge" doesn't necessarily mean "i'm writing a form letter and want to import addresses" is like pulling teeth. Word has no problem with just binding whatever data to a form. Polish(x1). Also, Word doesn't force you (or confuse you) into creating an Access database when you just want to import an informal list of crap from Excel. Writer DOES try to get you to make a Base
Now, none of these are absolute deal-breakers, nor do they show that OO.o is somehow unworthy of attention. On the contrary, it shows that OO.o needs more attention, and from people who actually use the features they're coding. MS Office will only get better if there's pressure on MS to make it better, and OO.o is probably the best hope for applying that kind of pressure. I just think that MS really deserves some credit for making Office a decent app suite. They've done far more than most
Just to clarify, none of this applies to the Windows vs. Linux debate. I want Windows to just go die in a fire. It really needs to be flushed like all the other turds.
We never used CocoaJava (Score:5, Insightful)
Disclaimer: I am a founder of the NeoOffice [neooffice.org] project.
Quote: and became an even worse idea when Apple deprecated the Java-Cocoa bridge
We never used the CocoaJava bridge at all. I guess you never bothered to read the source code. In fact, we use very little Java at all as is pointed out by the ohloh source code analysis [ohloh.net] of our open CVS. There's little Objective-C as we do most of the logic in C++ and call out to ObjC when required. There are some other stats there you may find intriguing as well like the estimated man-years and cost [ohloh.net] it will take to approximate our code.
Trust me, once any OS X port of OOo starts getting font handling and input methods correct, it'll slow down as well. This is true especially for Asian and other foreign languages. The bottleneck is in Apple's ATSUI and how it mismatches to the underlying OOo code. Has nothing to do with Java at all. Speed in a vaporware demo is one thing; carrying speed into a functional product is something different completely.
ed
Re:We never used CocoaJava (Score:5, Insightful)
If that's true (and I don't doubt that it is), then putting that "/J" in the name was a spectacularly bad idea.