NeoOffice/C

From NeoWiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 16:48, 19 August 2007 (edit)
Sardisson (Talk | contribs)
(use local image)
← Previous diff
Current revision (02:35, 25 August 2008) (edit) (undo)
Sardisson (Talk | contribs)
(remove the redundant Neo/C status page)
 
(One intermediate revision not shown.)
Line 1: Line 1:
 +{{obsolete}}
[[image:Neo.gif|NeoOffice®/C]] [[image:Neo.gif|NeoOffice®/C]]
Line 9: Line 10:
Basically, using Cocoa with OpenOffice.org would be a herculean effort, and not just a simple port job. The Cocoa worldview (idea of how an application should be designed, operate, and be coded) and that of OpenOffice.org are in stark contrast, and melding the two—or converting one to the other—proved unstable and unsustainable. One could not simply make a 'wrapper' around OpenOffice.org, but instead very large amounts of code (OpenOffice.org is 8 million lines of code) would have to be re-written, with lots of ugly hacks along the way. (For more detail, see posts of NeoOffice.org founder Ed Peterlin aka [[User:OPENSTEP|OPENSTEP]] in [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1600 this thread] and [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=3585#3585 this thread] on trinity.) Basically, using Cocoa with OpenOffice.org would be a herculean effort, and not just a simple port job. The Cocoa worldview (idea of how an application should be designed, operate, and be coded) and that of OpenOffice.org are in stark contrast, and melding the two—or converting one to the other—proved unstable and unsustainable. One could not simply make a 'wrapper' around OpenOffice.org, but instead very large amounts of code (OpenOffice.org is 8 million lines of code) would have to be re-written, with lots of ugly hacks along the way. (For more detail, see posts of NeoOffice.org founder Ed Peterlin aka [[User:OPENSTEP|OPENSTEP]] in [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&t=1600 this thread] and [http://trinity.neooffice.org/modules.php?name=Forums&file=viewtopic&p=3585#3585 this thread] on trinity.)
-Thus, a second approach to achieving native OS X look-and-feel was tried using Mac OS X's Java implementation instead of Cocoa to display Aqua. The result was NeoOffice/J (beginning with version 1.2, known simply as NeoOffice), which has supplanted NeoOffice/C as the actively developed Mac OS X project.+Thus, a second approach to achieving native Mac OS X look-and-feel was tried using Mac OS X's Java implementation instead of Cocoa to display Aqua. The result was NeoOffice/J (beginning with version 1.2, known simply as NeoOffice), which has supplanted NeoOffice/C as the actively developed Mac OS X project.
-* [[NeoOffice/C_Status|Is NeoOffice/C Still Being Developed?]] 
* [[NeoOffice/C_Build_Instructions|How Do I Build NeoOffice/C?]] * [[NeoOffice/C_Build_Instructions|How Do I Build NeoOffice/C?]]
* [[Contributing_to_the_NeoOffice_projects|How Can I Contribute?]] * [[Contributing_to_the_NeoOffice_projects|How Can I Contribute?]]
[[Category:NeoOffice/C]] [[Category:NeoOffice/C]]

Current revision

Obsolete! (click icon for its license info)
This page is obsolete; it refers to an application that is no longer developed and is unsupported.

The information provided on this page remains available only for historical purposes.

NeoOffice®/C

Note: Until late 2004 NeoOffice/C was named simply "NeoOffice" (without the "/C"). This caused confusion, so in December 2004, the classic Cocoa/CoreGraphics version of NeoOffice was renamed to NeoOffice/C.

NeoOffice/C was a prototyping project—not intended for day-to-day use—used to explore methods and problems that may be encountered when porting OpenOffice.org to run natively on Mac OS X.

NeoOffice/C was in development for quite a while (see old screenshots here and here) when it became apparent the approach it was using was slow and impractical.

Basically, using Cocoa with OpenOffice.org would be a herculean effort, and not just a simple port job. The Cocoa worldview (idea of how an application should be designed, operate, and be coded) and that of OpenOffice.org are in stark contrast, and melding the two—or converting one to the other—proved unstable and unsustainable. One could not simply make a 'wrapper' around OpenOffice.org, but instead very large amounts of code (OpenOffice.org is 8 million lines of code) would have to be re-written, with lots of ugly hacks along the way. (For more detail, see posts of NeoOffice.org founder Ed Peterlin aka OPENSTEP in this thread and this thread on trinity.)

Thus, a second approach to achieving native Mac OS X look-and-feel was tried using Mac OS X's Java implementation instead of Cocoa to display Aqua. The result was NeoOffice/J (beginning with version 1.2, known simply as NeoOffice), which has supplanted NeoOffice/C as the actively developed Mac OS X project.

Personal tools