Hi James, Am Sat, 31 Dec 2005 03:02:44 -0700, schrieb James McKenzie: > I don't know. You have a project that I cannot (or have not) been able > to get at the source for as of yet. Patrick/Ed/Dan and others put their > efforts on the NeoOffice.org site and this code is available for public > download from the cvs server (like that at OpenOffice.org). Are you > willing to put your team's efforts out for the rest of the world to look > at, discuss at length and help fix/improve if necessary? If so, please > let us know where the sources are at so we can look at them and suggest > improvements. I know it is very early in your efforts, but at this time > I have doubts that this will EVER happen (and the emphasis is there for > a reason.)
I assume that you read this list here and that you read mac porting list. If so you know where to get the code for our OOo. Over the last days Eric Bachard posted a few messages where he provided a list of to-do's for 2.0.2 and which issues do cover this. In other posts he and other mentioned enough child workspaces etc ppp which have the code for the issues. So all you have to do is checkout the main OOo source code for 2.0.1 or and the child workspaces mentioned to get the appropriate code for the work that the Mac Porters have done. Even Florian Heckls first steps towards native OOo are available in a child workspace. > Keeping your project secret is not in the spirit of Open > Source and makes the rest of us wonder if it even exists. What Eric and others do is that they keep patches on their machines as long as they are not sure if they work or not. Once their patches solve the problem they get into a child workspace. Maybe we can discsss if it is a good idea or not to make non-working patches available. But once the patch is in the cws. Check out the cws and you can examine if the patch is righ, wrong or if you have a better solution. > The question in my mind is: Does sources exist for your project, where are they and > what type of license are they going to be released under. The sources are right here. You can get them immediately. Go through the messages on porting and mac porting and note out the mentionend cws. Eric B and others don't plan a new project. They want to make the existing OOo Aqua native and again the sources are available. CWS is afaik aquavcl. Take a look at it in EIS <http://eis.services.openoffice.org/EIS2/servlet/GuestLogon> > And I'm definately working on a port of OpenOffice to the Mac that works > TODAY. I'm not going to wait for a project that may see results in two > to three YEARS. And this is without the support of SUN or any other > major company. This is something to keep in mind when you start a new > project. Will this project create a new and better product or is it > best to help an already existing project improve to the point where your > efforts are recognized. It appears that you want much glory and if you > succeed, this may/may not happen. However, pointing out the failures of > others does not do much to help your effort and may actually have a > counterproductive effect. Getting personal and emotonial isn't right here. I had to learn this too. So please only discuss about the issues of work and not on the personal site. As written earliere by me. I think that neither you nor Mox do any harm to us or to Neo/J folks. Thanks Kind reagards and a happy new year to all of us. Eric Hoch -- ## Ansprechpartner Anwenderunterstützung, users-Mailingliste, MacOSX ## de.OpenOffice.org - Office für MacOS X, Linux, Solaris & Windows ## Openoffice.org - ich steck mit drin! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
