Dear Eric, Sorry, I missed that keyboard issue. It was 1 AM at the time of reading and writing. But my point stands: the milestone builds for the Mac are not of release quality yet.
It pains me to read that your consider Neo/J's development as stealing. I prefer to think of it as a multistage rocket, with the OOo linux/windows version as the first phase, the Mac port as the second and the Neo shell as the third. All three are needed to reach the Mac 'heavens'. I have the idea that this is the sort of bug that Patrick has made fixes for in the past when none were forthcoming here, and the sort of code he would donate back. To my limited knowledge, he has donated fixes to OOo code he made in the process of creating Neo/J. I understand your disappoinment, but please consider that Patrick has spent a lot of time on Neo/J as well. At this moment he may not be familiar with the 2.0 code and would require a lot of time to properly port the code he donated. At the same time he and Ed are preparing for Mactel and moving the Neo/J specific code to Java 1.4 and Cocoa. Only after that do they envision a move to the 2.0 codebase. Resources are also limited. At the moment NeoOffice coding is done by about 2.5 people. That is not a lot of manpower and diluting it to cover this project as well may not help., especially because fixing OOo 2 is a running target. When NeoOffice is ready to move to the 2.0 codebase, our paths will join more closely again, and I am confident Patrick and Ed will be inclined to help you out. In terms of licensing, we have been through this and I don't intend to get into that argument: Patrick does not want Sun to create a proprietary version based on his volunteer work. That would have someone else profit of his community work and I respect that, whatever limitations it entails. Some proposals were given some time ago (like putting the whole Mac effort under LGPL/GPL only), but no movement has occured on this front. Since I haven't written any code, I feel I am not in a position to pursue this further. Best wishes, Oscar P.S. Sophie, Jean-Christophe Helary informed me that by NL you may have meant Native Languages. In that case, I can only say that Patrick has spent an awful lot of time to get all sort of NL input and fonts to work, again making full use of the localization and internationalization efforts done with OOo in general. Apologies for the confusion - NL is the common language/country code for the Netherlands and I happen to live there. > I know it is much easier to read only what one wants to read and to > blame OOo for every bug that occures in NO/J then do something and > help OOo fixing the bug. > > I appreciate the hard work of Ed and Patrick in giving OOo a native > GUI and I also appreciate the code donation Patrick made but what I > cannot see is that they help getting OOo 2.0 stable. Would it be so > hard for Patrick or Ed to help us adopting his fixes to OOo 2.0 > tree and not only donate the code? This would be real teamwork and > not only donate the code, let us OOo porters do the work, "steal" > the code when porting to 2.0 is done, wrap NO/J around it, use GPL > so that the code is useless for OOo, wait till OOo 2.x or 3.x > arrives, again give back some code, again don't do anything in > porting it and so on. > Ed and Patrick in addition would benefit from this kind of > teamwork. The sooner OOo 2.0 X11 for Mac OS X is stable, the sooner > could they wrap NO/J around it. > > Regards, > 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]
