Hi Steven,

Le 3 oct. 07 à 20:23, Steven G. Johnson a écrit :

Dear OOo Mac developers,

I do a lot of (mostly scientific/numerical) software development on GNU/Linux, and am very familiar with autoconf etc.,

Good :-)


although I use MacOS X as my desktop machine and many years ago wrote GUI software for MacOS (pre X).
I'm eagerly looking forward to the Aqua version of OOo,

You are welcome : do you want to test our developper builds ?


but I wondered if there was any chance of getting it working on MacOS 10.2 or 10.3.

Honestly, I don't think so for 10.2 : 10.2 needs a lot of stuff, and does use a prehistoric compiler. For 10.3, an since we switched to Cocoa, I don't know. I remember Quartz issues with possible compatibilities, but this would cause hackish patches ..

FYI, the build is currently broken (X11 can imho build), maybe we can fix a lot of breaks, but Aqua build will need a lot of work for 10.3.



The reason I ask is that my mother works with computers at an elementary school that uses a lot of Macintoshes, and they are currently facing a transition away from AppleWorks (which is being discontinued by Apple). OpenOffice.org seems like it would be a great alternative for them.


Everything is possible, but maybe the amount of work is too much for the expected results. I hope I'm wrong ...


However, they have a large number of older computers still running MacOS 10.2 and 10.3,
and may not be able to upgrade them in the near term.


I understand.


I was thinking about working on a port to 10.2 this December or January based on your latest Aqua sources at that point in time.

If you really want to give it a try, please checkout 1.1.x sources, since you'll have to use and adpat to 2.x the included dlopen() stuff (in external if I'm not wrong) and locale things .. and probably more


Before I did so, however, I wanted to get a sense of how difficult this might be and whether other developers have any interest in older MacOS systems.

This is not they are not interested, but I think Mac porters are not enough, and are most of the time running after Apple, forcing them to always update :-/


Can you give me a quick opinion of this?

See above


Is it just a matter of futzing a bit with the build procedure, header files, commenting out a bit here and there, etc?

(from memory) if I'm not wrong, dlopen() was still needed in 10.2, not in 10.3. They are other locales issues and other goodies in sal, graphical issues in vcl ( we use Quartz ) ... etc .. this is not clear


Would you accept patches for backwards compatibility?


Sure we will !!  Be welcome on Mac OS X porting project :-)



  Or are 10.4-only features deeply woven into the codebase?

See above  ...


Regards,
Eric Bachard


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to