Difference between revisions of "Mac OS X Porting - contributions from NeoOffice"
Line 1: | Line 1: | ||
+ | ==Introduction== | ||
+ | Collaboration between OpenOffice.org and the NeoOffice -project has an ugly history. It is one of those things | ||
+ | that one finds hard to be neutral about. You either hate NeoOffice, or love their work. | ||
+ | Despite this, there has been smaller and bigger contributions coming from NeoOffice to OpenOffice.org, every once | ||
+ | in a while. It's very far from perfect, but it's something. | ||
+ | We at OpenOffice.org must stop hating others and spreading bad words. Our attitude must be honorable, no matter what others do. | ||
+ | The purpose of this page is to record all the contributions NeoOffice has done to OpenOffice.org. Maybe this makes one appreciate the history more. | ||
+ | ==The philosophical differences== | ||
+ | |||
+ | '''Anonymous:''' | ||
+ | The OpenOffice.org is a work in progress, and you'd better to support the real OpenOffice.org project, instead of propagate a big lie. | ||
+ | As long as OpenOffice.org people have this kind of attitude towards NeoOffice, I see no reason why NeoOffice | ||
+ | people would want to cooperate with OpenOffice. | ||
+ | |||
+ | - Mox | ||
+ | '''Anonymous:''' | ||
+ | As summary : NeoOffice IS NOT OPENOFFICE.ORG | ||
− | + | With NeoOffice using & including something like 95% of the code in openoffice.org CVS, I find your | |
+ | summary somewhat misguiding. | ||
+ | |||
+ | This issue and the "not native because UI is partly(!) in Java" are clear signs how NeoOffice developers | ||
+ | (who are user-oriented developers) differ from OpenOffce.org developers (who are mainly coder-oriented) | ||
+ | |||
+ | '''Have you seen this?''' | ||
+ | "If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, | ||
+ | and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee | ||
+ | is irrelevant." | ||
+ | [http://neowiki.sixthcrusade.com/index.php/NeoOffice_and_Aqua NeoOffice and Aqua] | ||
+ | |||
+ | Users do not care if the UI is in Cocoa (the hot chocolate) or partly in Java (Coffee). To users the Java UI | ||
+ | is "Native" and NeoOffice is "OpenOffice derivative", because NeoOffice looks like OpenOffice, behaves like | ||
+ | OpenOffice, has the (at least) the same functionality and same menus. | ||
+ | |||
+ | As a developer you can disagree to this. But then you are not speaking to the people who use the actual | ||
+ | application. You are speaking coder-speak. | ||
+ | |||
+ | Now, the entirely different matter is that the openoffice.org _as organisation_ is not the same as the | ||
+ | organisation that builds NeoOffice. But that distinction does not prevent the NeoOffice being called | ||
+ | OpenOffice.org -derivative or similar things. | ||
+ | |||
+ | |||
+ | '''"Hate leads to anger and anger leads to the dark side" - Yoda.''' | ||
+ | |||
+ | - Mox | ||
+ | ... | ||
Revision as of 08:41, 24 November 2006
Introduction
Collaboration between OpenOffice.org and the NeoOffice -project has an ugly history. It is one of those things that one finds hard to be neutral about. You either hate NeoOffice, or love their work.
Despite this, there has been smaller and bigger contributions coming from NeoOffice to OpenOffice.org, every once in a while. It's very far from perfect, but it's something.
We at OpenOffice.org must stop hating others and spreading bad words. Our attitude must be honorable, no matter what others do.
The purpose of this page is to record all the contributions NeoOffice has done to OpenOffice.org. Maybe this makes one appreciate the history more.
The philosophical differences
Anonymous: The OpenOffice.org is a work in progress, and you'd better to support the real OpenOffice.org project, instead of propagate a big lie.
As long as OpenOffice.org people have this kind of attitude towards NeoOffice, I see no reason why NeoOffice people would want to cooperate with OpenOffice. - Mox
Anonymous:
As summary : NeoOffice IS NOT OPENOFFICE.ORG
With NeoOffice using & including something like 95% of the code in openoffice.org CVS, I find your summary somewhat misguiding. This issue and the "not native because UI is partly(!) in Java" are clear signs how NeoOffice developers (who are user-oriented developers) differ from OpenOffce.org developers (who are mainly coder-oriented) Have you seen this? "If it looks like a duck, walks like a duck, and quacks like a duck, then to the end user it's a duck, and end users have made it pretty clear they want a duck; whether the duck drinks hot chocolate or coffee is irrelevant." NeoOffice and Aqua Users do not care if the UI is in Cocoa (the hot chocolate) or partly in Java (Coffee). To users the Java UI is "Native" and NeoOffice is "OpenOffice derivative", because NeoOffice looks like OpenOffice, behaves like OpenOffice, has the (at least) the same functionality and same menus. As a developer you can disagree to this. But then you are not speaking to the people who use the actual application. You are speaking coder-speak. Now, the entirely different matter is that the openoffice.org _as organisation_ is not the same as the organisation that builds NeoOffice. But that distinction does not prevent the NeoOffice being called OpenOffice.org -derivative or similar things. "Hate leads to anger and anger leads to the dark side" - Yoda. - Mox
...