Hi Terry,
Terry Teague a �crit :
At 12:57 PM +0100 2/21/05, eric.bachard wrote:
Sorry I have been busy lately, and wasn't able to look at this until today.
Not a problem, we all have not enough of 24h in a day :-)
I appreciate the efforts you and others have made on this.
You're welcome :-)
I have some of the same comments as others - Mac users expect /Applications rather /opt.
Yes, sure it's a big mistake to not take care of what Mac User want !
For memory :
Aqua like Easy Installation Same shortcuts as Mac OS X API Easy copy-paste D'nD Use Apple fonts
(Ufff....we have a lot of work :-) )
After the install was complete, the OOo install folder window came to the front (good), but I forgot that the Installer was still running (finished)
You think to the experimental version I have uploaded ? (not sure to understand). The latest I have uploaded opens /opt directory (for en-US ) version, and /Applications for french version. This is simple a postinstall shell script (open -a ... directory ). I'll had the new official splashscreen in background for next version (m82 is building).
- I don't think it had an adverse effect, but there might be some better ways to handle things.
It work's fine.
- fix libxml2 bug (version mismatch sometimes)
I ran into this and was not able to get past it - I can't see how this could happen "sometimes" - I would expect it to happen every time on
I completely agree with you ( yes, how can this happens ? ), but that's exactly what testers reported, and I must take care of this.
Two problems can occur :
The first was caused with old libxml2 version, causing a mismatch with System (even while building). With 2.6.11 or something like that in System libraries and 2.6.1{1 | 3} in OOo, in some conditions, mismatch occurs. Just renaming libxml2 fixes this, but we cannot ask a "generic Mac User" to modify something in the system :-)
One tester reported me that the fix (in his case) was rename libxml2.2.6.17.dylib libxml2.2.dylib in $INSTALL_DIR/program/
For the second, it is only because when --enable-gtk is used (I use it, even it is not completely functionnal yet)), some parts of libgnomevfs are used. libxml2 < 2.6.14 don't have such symbols inside while libxml2 >2.6.14 has.
This problem can simply causes crashes (workaround consists in simply use OpenOffice.org dialog boxes in options )
If I remember correctly, Caolan fixes this in cmcfixes01 (not sure at all of the cws name).
That's the reason why I prefer follow this problem
Since *2.6.17* is used (since m78, if I'm not wrong), this problem should IMHO be fixed.
specific configurations. I was running OOo on Mac OS X 10.3.3, which has libxml2.2, and the error message refers to the compatibility version 9.0.0 being higher than the library version 8.0.0.
This problem is solved, it's a new one, libgnomevfs relative.
What version of Mac OS X are you building on?
10.3.4
I prefer not update, for compatibility reason. Do you think it's a good thing or not ? (everything works fine for me, and sometimes Apple update are...dangerous...)
Of course, as Ed pointed out, this installer solution only works for Panther (and I assume Tiger) users, not for Jaguar users.
Yes, recurrent problem... :-/
I guess when OOo
2.0 is released, we will produce a Jaguar based US English OOo 2.0 for Mac OS X installation.
Yes, 10.2 users. A day, I'll reinstall Jaguar. I just am not sure of the minimal gcc version needed for the build. On Linux, gcc-3.4 seems to be the good one. One Mac OS X, we're XCode dependant :-/ (Mac OSX is not free... )
Re "Start_OOo" or "Begin_OOo" - you were asking about ownership - I don't know why you just didn't contact me directly.
Sorry, my mistake. I thought it was a public question...
Anyway, the original "Start
OpenOffice.org" is mine, and Kevin based his "Begin_OOo" on that for the Panther installers.
Ok, noticed
What you have in your installer package is some kind of
mixture.
Yes, and that's the reason why I ask. I wasn't sure.
I have fixed some bugs in "Start OpenOffice.org" since the last
release (v1.0b9), and if there is any additional work to be done for 2.0, I would try to do that, as well as fix some more bugs and make improvements I have planned, in time for OOo 2.0 on Mac OS X.
I am very interested to understand how it works exactly ( XCode helps me a lot) and which improvements you have planned. Of course, if I can, I'd be interested to help you too :-)
For now, I'm learning Cocoa and begin to play xith XCode.
The actual state of art of the installation is issued, and I invite you to have a look at <http://qa.openoffice.org/issues/show_bug.cgi?id=42998> , you'll read what is missing is *just* the (third actually) part I incorporate for french project builds.
To make short, what is always missing is something :
- Cocoa compliant - able to be D'nDropped in the dock - able to launch OOo with simple click
Bonus can be the use of fondu, using OOo_Admin ? IMHO, it is a very good solution.
BTW, about fondu, I have my own build, packaged by myself, with a fixe about Japanese and some complexes fonts (tip from Etsuchi Kato). If I'm not wrong, fondu is under GPL, including all my changes.
What I don't know yet is if we can incorporate or not all the stuff because of license problems....
If it is possible, I think we have a complete solution, if not, I propose to rewrite myself all the necessary code to do the same actions, but under usable license for OOo project. I know it is stupid somewhere, but LGPL is poisoning us sometimes...
Whether "Start
OpenOffice.org" should be part of "your" installation, or available separately, is something we can discuss (perhaps offline).
No problem, you're welcome :-)
Regards, eric bachard
--
eric bachard <[EMAIL PROTECTED]>
French OpenOffice.org Community contributor (build of french releases for Linux PPC and Mac OS X / X11)
See : <http://fr.openoffice.org>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
