The current (2006) OpenOffice 2.x X11 port for Mac OS X continues to benefit from this pioneer work. Not the least because of the bridges -module, which requires platform specific assembler language(!) -coding. The linux/unix X11 port of of course existed already, but because of code base, the porting to Mac OS X was still a herculean task. The three core developers worked on Mac OS X for X Windows (X11) port, starting completely from scratch. Terry Teague - maintainer of Start -script, which was needed for OOo 1.1 (Terry Teague died suddenly and was a great contributor to both projects).With some other contributors infrequent contributors such as: Patrick Luby - After OOo 1.1 went to co-found the NeoOffice project.Ed Peterlin - After OOo 1.1 went to co-found the NeoOffice project.Dan Williams - After OOo 1.1 left completely the scene.The Mac OS X porting team in at that time consisted from three (3) core developers: When talking to users, we must agree with them that the two applications are similar.Ĭontributions in the 1.x timeframe (years 2000-2003) We do not want to confuse or anger the users. Users look at NeoOffice and say that it is very similar to.Coders look at NeoOffice and say that it is very different from.There is a difference in speech between coders and users: NeoOffice is similar to (NeoOffice has same menus, (at least) same functionality and almost the same look as ).NeoOffice is based on (The GPL license in NeoOffice permits including LGPL licensed code).NeoOffice is a derivative of (about 95% of code in NeoOffice comes from CVS). While respecting the above rights, it is completely LEGAL and correct to say: general feedback from one project to the other.related to Apple HIG), or just lots of beer joint collaboration on design and feature specification/priorisation, or with new APIs (e.g.NeoOffice contributing to small or bigger fixes that they have fixed in NeoOffice, but are not in.friendly behaviour towards the "other" project, no matter what opinions the others have.Although it is very unlikely that things will get better any time soon.Īny one of these actions would significantly help the situation: It should be noted that several individuals in NeoOffice and -projects continue efforts to "mend the bridge" between these two projects. In 2006, there was a decision by the organization to move all information about to the derivatives page, as is and will continue to be a derivative. This effort is using different approach than NeoOffice - The team uses Carbon/Cocoa for the GUI wrapper. The 's native Mac OS X porting effort is called Aqua. Since around 2004 or 2005, there has been a new Mac OS X porting team in, lead by Eric Bachard. For this reason NeoOffice project is not supported by. Since only accepts LGPL licenced code, it is not possible to directly include NeoOffice code in. The parts of code that are only in NeoOffice, are under GPL licence (e.g. What this project basically did, was to use Carbon/Java to create a GUI wrapper around the basic application code. The NeoOffice project has lead to a native Mac -looking derivative of. (Details are not available as to what happened and why.) This resulted in the original group leaving the community and founding a project of their own: NeoOffice. There was a falling out of sorts between the community and Sun Microsystems, who was Patrick's employer at the time. for Mac OS X porting efforts were started by the original Mac OS X porting team: Patrick Luby, Ed Peterlin, Dan Williams, et. Maybe this makes one appreciate the history more. The purpose of this page is to record all the contributions NeoOffice has done to. Our attitude must be honorable, no matter what others do. We at must stop hating others and spreading bad words. It's very far from perfect, but it's something. You either hate NeoOffice, or love their work.ĭespite this, there has been smaller and bigger contributions coming from NeoOffice to, every once
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |