Difference between revisions of "FAQ OpenOffice.org and NeoOffice"

From Apache OpenOffice Wiki
Jump to: navigation, search
m
 
(104 intermediate revisions by 14 users not shown)
Line 1: Line 1:
=== What is NeoOffice? ===
+
{{Documentation/Candidate}}
[http://www.neooffice.org NeoOffice] is a version of [http://www.openoffice.org/ OpenOffice.org] for Mac OS X that is specially focused on making OpenOffice.org user-friendly and easy to use for end users. It is currently (as of Jan 2006) the only version of OpenOffice.org that has good native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X, native menus, native printing, native drag and drop, native cut and paste, and also native access to all files, links, aliases and (mounted) volumes on the Mac OS X system.
+
  
'''For developers:''' NeoOffice uses GPL license and is built on top of OpenOffice.org X11 by using Cocoa and Java for the User Interface (UI).
+
=== What is OpenOffice.org ===
  
More information on NeoOffice in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]
+
[http://www.openoffice.org/ '''OpenOffice.org'''] is the name of productivity application suite, the project and the website. Please note the '''.org''' part of the project name, which is needed for legal reasons.
  
=== What is OpenOffice.org X11 for Mac OS X / Darwin PPC?===
+
Users and many organizations benefit from the power and the generous license of the project. The original license even allowed taking all the code, documentation, templates, etc. and not contributing anything back into the project. This resulted in many forks:
OpenOffice.org X11 is a version of OpenOffice.org (OOo for short) that uses the UNIX system, that the Mac OS X is based on. So, the OpenOffice.org X11 behaves like a UNIX program within Mac OS X. While the program can be used quite productively on Mac OS X system, it has lesser amount of integration with the system then NeoOffice. If you are an experienced Mac OS X user or familiar with UNIX systems (e.g. Linux), then you should be able to work with OpenOffice.org with relatively little effort.
+
* the core project: OpenOffice.org
 +
* StarOffice (from SUN)
 +
* Lotus Symphony (from IBM)
 +
* RedOffice (from RedFlag)
 +
* Go-OOo (from Novell)
 +
* OxygenOffice
 +
* NeoOffice (from Planamesa)
 +
* PlusOffice( from OpenZone)
 +
* Luxuriosity Office
 +
* MagyarOffice
 +
* etc.
  
'''For developers:''' OpenOffice.org X11 uses LGPL license and is developed within openoffice.org CVS. You will also have to sign a [http://contributing.openoffice.org/programming.html JCA] (read the bottom of the page) to contribute to the effort.
+
There are different kinds of collaboration between the projects. They all have in common that they take the new features, improvements, and the many bugfixes from the core project and extend it to their needs. Some of the projects contribute all their changes back. Some projects contribute developer power for isolating problems. Some projects contribute by writing good bug reports to get the upstream developers involved.  Some projects just replace the branding and sell it as their product. Some just take and never give back and instead threaten with lawsuits if the core project touches their niche market.
  
More information about OpenOffice.org X11 in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages]
+
Since specialized needs of these forks are sometimes not directly applicable to the core project and the effort needed to integrate their changes into such a complex multi-platform, multi-language office suite require valuable development and testing resources there will always be the temporary need for specialized branches of the core project. The core project aims to be as generally useful as possible, so the need of forks is reduced.
  
=== What is OpenOffice.org Aqua port / Cocoa port?===
+
=== OpenOffice.org Aqua ===
Starting in October 2005, there has been an effort to revive the direct native port of OpenOffice.org for Mac OS X. Currently (Jan 2006) this effort is at its first stages and it will take a long time, before it will be ready for final release. News about this effort will be published in [http://porting.openoffice.org/mac/ OpenOffice.org Mac porting pages].
+
  
---
+
[http://porting.openoffice.org/mac/ OpenOffice.org Aqua] is the OpenOffice.org core project with native support for Mac Aqua. Since version 3.0 of OpenOffice.org was released Mac Aqua is another primary platform of the core project.
  
=== Q1: Why there seems to be several parallel efforts? ===
+
Mac OS X port Home: [[http://porting.openoffice.org/mac/ Mac OS X port Home]]
Well '''shortly''': because this is very normal situation in open source. And because of historical and personal choices.
+
Aqua links: [[http://wiki.services.openoffice.org/wiki/Category:Aqua Aqua Version of OpenOffice.org]]
 +
Blogs: [[http://porting.openoffice.org/mac/links.html Developers blogs]]
  
We encourage you to read first the [http://www.planamesa.com/neojava/en/faq.php NeoOffice FAQ].
+
=== What is NeoOffice? ===
  
reasonably astable version of the OpenOffice.org office suite that has been engineered to run natively on Mac OS X.
+
[http://www.neooffice.org NeoOffice] is a fork of the core project, which specialized in making it available for Mac OS X independently from [[FAQ_Openoffice.org_and_NeoOffice#OpenOffice.org_Aqua | OpenOffice.org's Aqua]] port mentioned above.
  
This page is a copy-paste, will be edited soon properly.
+
Fork meaning that NeoOffice is another project, and is not OpenOffice.org. The NeoOffice project does not contribute back to OpenOffice.org and usually does not help to enhance the core project.
 +
 
 +
Using Java/Cocoa binding,  its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way). It is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).
 +
 
 +
NeoOffice used a subclause of OpenOffice.org's license to change it to another license which is incompatible with the core project. so, to avoid legal issues, OpenOffice.org developers had to rewrite some subsystems, since NeoOffice code cannot be used in OpenOffice.org. Even when the licence for a fork change was compatible with the core project other kinds of legal threats were [http://council.openoffice.org/servlets/ReadMsg?list=discuss&msgNo=1187 were used].
 +
 
 +
More informations in [http://neowiki.sixthcrusade.com/index.php/NeoJInfo About NeoOffice]
  
 
----
 
----
=== Q1 ===
 
A: The [http://trinity.neooffice.org/modules.php?name=Forums&file=index&c=7 NeoOffice forums]
 
provide most of the user support for OOo X11. The NeoOffice people are helping there.
 
  
=== Q2 ===
+
=== Q1: Where can I find OpenOffice.org or NeoOffice? ===
A: One has to separate the users and the developers, they need different things and not all the users want to do development.
+
'''A:''' You can download both from respective sites.
Also the NeoOffice people actively need OpenOffice X11 to create NeoOffice, so there is strong dependency between them.
+
 
Sometimes there is extra need to communicate things from NeoOffice to OOo and vice versa, but this is just a small thing that can be solved and is mostly working very well currently. NeoOffice and OOo are a JOINT community.
+
[http://download.openoffice.org/ Download OpenOffice.org from here] (openoffice.org)
 +
 
 +
[http://trinity.neooffice.org/modules.php?name=Downloads Download NeoOffice from here] (neooffice.org)
 +
 
 +
=== Q2: Why does there seem to be several parallel efforts? ===
 +
'''A:''' This is a very normal situation in open source. And because of historical and personal choices.
 +
 +
This [http://porting.openoffice.org/servlets/ReadMsg?list=dev&msgNo=14452 mail from Kevin Hendricks] provides some historical details.
 +
 
 +
If you want to really understand the situation, here's some additional reading for you: [http://neowiki.sixthcrusade.com/index.php/History_of_NeoOffice_and_OpenOffice.org:_Introduction History of NeoOffice and OpenOffice.org], [http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=125 Quote from Patrick] may explain some of the licensing situation, and finally, you may also want to read [http://www.planamesa.com/neojava/en/faq.php another FAQ]
 +
 
 +
=== Q3: Where do I get support for OpenOffice.org Mac/Aqua ? ===
 +
'''A:''' The [http://support.openoffice.org/ OpenOffice.org support page] is the starting point for all support related to core project.
 +
 
 +
=== Q4: It's OpenSource, so one project should freely use the other projects code ===
 +
'''A:''' Due to license incompatibilities this is not possible.
 +
 
 +
In the OpenSource world there were always issues with license incompatibilities, e.g. switching the license of [http://en.wikipedia.org/wiki/BSD_license revised-BSD]-code to [http://en.wikipedia.org/wiki/GNU_General_Public_License GPL] has always been legal, the reverse is not true though. Since a change like that is one-way only and prevents the generous original project from receiving fixes from the derived project, this is usually considered an unfriendly act.
 +
 
 +
=== Q5: But it would be more efficient, if there would be only one effort...===
 +
'''A:''' Probably. A proposal to work together has been made, and NeoOffice developers refused.
 +
 
 +
OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is '''community project'''.
 +
 
 +
The NeoOffice project is a Patrick Luby and Ed Peterlin project only.
  
=== Q3 ===
+
The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, '''because of the licensing issues'''.  
A: NeoOffice is a product that builds on top of OpenOffice X11, it is not really doing the same work as OOo X11. If you complain that everybody should be doing the same port (i.e. the GPL/Java versus LGPL/Cocoa), then you are really complaining that there should not be both KDE and Gnome, only one of those. Those who write code have the freedom to choose the licence/toolkit for their own code, it's their work and their rights.
+
So every change must be rewritten for OpenOffice.org project, using another implementation.
  
=== Q4 ===
+
A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org, since OpenOffice.org project wants to use only Cocoa/Carbon.
A: The fact is that NeoOffice is ready for end users NOW, and it uses OpenOffice. So that's the best way to get more _happy_ OOo users to the world. When OOo Cocoa is ready, then we can compare which is more user friendly and make decisions and recommendations based on that.
+
  
=== Q5 ===
+
Further information is available at: '''https://www.openoffice.org/porting/mac/'''
A: NeoOffice is not taking developers away from OOo: no matter what codebase is used, OOo X11 will get the important fixes and patches sooner or later. The Java part of NeoOffice is not interesting for OOo since OOo wants to use Cocoa/Carbon. Otherwise people could have started contributing to Java on NeoOffice in the first place.
+
  
=== Q6 ===
+
[[Category:MacOSX]]
A: People, stop being so hostile to projects that are not "your own"!
+
[[Category:Aqua]]
 +
[[Category:Documentation/FAQ]]

Latest revision as of 12:45, 13 April 2022


What is OpenOffice.org

OpenOffice.org is the name of productivity application suite, the project and the website. Please note the .org part of the project name, which is needed for legal reasons.

Users and many organizations benefit from the power and the generous license of the project. The original license even allowed taking all the code, documentation, templates, etc. and not contributing anything back into the project. This resulted in many forks:

  • the core project: OpenOffice.org
  • StarOffice (from SUN)
  • Lotus Symphony (from IBM)
  • RedOffice (from RedFlag)
  • Go-OOo (from Novell)
  • OxygenOffice
  • NeoOffice (from Planamesa)
  • PlusOffice( from OpenZone)
  • Luxuriosity Office
  • MagyarOffice
  • etc.

There are different kinds of collaboration between the projects. They all have in common that they take the new features, improvements, and the many bugfixes from the core project and extend it to their needs. Some of the projects contribute all their changes back. Some projects contribute developer power for isolating problems. Some projects contribute by writing good bug reports to get the upstream developers involved. Some projects just replace the branding and sell it as their product. Some just take and never give back and instead threaten with lawsuits if the core project touches their niche market.

Since specialized needs of these forks are sometimes not directly applicable to the core project and the effort needed to integrate their changes into such a complex multi-platform, multi-language office suite require valuable development and testing resources there will always be the temporary need for specialized branches of the core project. The core project aims to be as generally useful as possible, so the need of forks is reduced.

OpenOffice.org Aqua

OpenOffice.org Aqua is the OpenOffice.org core project with native support for Mac Aqua. Since version 3.0 of OpenOffice.org was released Mac Aqua is another primary platform of the core project.

Mac OS X port Home: [Mac OS X port Home] Aqua links: [Aqua Version of OpenOffice.org] Blogs: [Developers blogs]

What is NeoOffice?

NeoOffice is a fork of the core project, which specialized in making it available for Mac OS X independently from OpenOffice.org's Aqua port mentioned above.

Fork meaning that NeoOffice is another project, and is not OpenOffice.org. The NeoOffice project does not contribute back to OpenOffice.org and usually does not help to enhance the core project.

Using Java/Cocoa binding, its look is like native integration with the Mac OS X system. This means, for example, native access to all the fonts in Mac OS X a different way than OpenOffice.org does (OpenOffice.org does use all Apple fonts, but not the same way). It is built on top of OpenOffice.org X11 by using Java/Cocoa bindings for the User Interface (UI).

NeoOffice used a subclause of OpenOffice.org's license to change it to another license which is incompatible with the core project. so, to avoid legal issues, OpenOffice.org developers had to rewrite some subsystems, since NeoOffice code cannot be used in OpenOffice.org. Even when the licence for a fork change was compatible with the core project other kinds of legal threats were were used.

More informations in About NeoOffice


Q1: Where can I find OpenOffice.org or NeoOffice?

A: You can download both from respective sites.

Download OpenOffice.org from here (openoffice.org)

Download NeoOffice from here (neooffice.org)

Q2: Why does there seem to be several parallel efforts?

A: This is a very normal situation in open source. And because of historical and personal choices.

This mail from Kevin Hendricks provides some historical details.

If you want to really understand the situation, here's some additional reading for you: History of NeoOffice and OpenOffice.org, Quote from Patrick may explain some of the licensing situation, and finally, you may also want to read another FAQ

Q3: Where do I get support for OpenOffice.org Mac/Aqua ?

A: The OpenOffice.org support page is the starting point for all support related to core project.

Q4: It's OpenSource, so one project should freely use the other projects code

A: Due to license incompatibilities this is not possible.

In the OpenSource world there were always issues with license incompatibilities, e.g. switching the license of revised-BSD-code to GPL has always been legal, the reverse is not true though. Since a change like that is one-way only and prevents the generous original project from receiving fixes from the derived project, this is usually considered an unfriendly act.

Q5: But it would be more efficient, if there would be only one effort...

A: Probably. A proposal to work together has been made, and NeoOffice developers refused.

OpenOffice.org does concern several developers who are working on their free time only. Any change is for OpenOffice.org project, and the name of the developer who wrote the code does not appear in the code after integration : this is community project.

The NeoOffice project is a Patrick Luby and Ed Peterlin project only.

The problem is : there is curently no possibility for OpenOffice.org to use NeoOffice code, even if this code is interesting, because of the licensing issues. So every change must be rewritten for OpenOffice.org project, using another implementation.

A big part of changes are using Java in NeoOffice, and this is as wrote Ed Peterlin, a short term choice. The Java part of NeoOffice is not interesting for OpenOffice.org, since OpenOffice.org project wants to use only Cocoa/Carbon.

Further information is available at: https://www.openoffice.org/porting/mac/

Personal tools