> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 24, 2001 6:00 AM
> With the advent of OSX and Carbon, the number of options and
> combinations for mozilla are staggering. We'd like to get a feel for
> where our external embedding customers would like to see us focus our
> limited resources.
>
> The options are plentiful, but our questions boil down to these:
> - if your app runs on OSX, does the same build need to run on
> OS9 as well?
I'd prefer this but separate builds would be OK. I know people who
are wary of moving to OS X, and so OS 9 support will be needed for a
while yet.
> - is being able to build with free tools important?
It would be nice, but not necessarily essential for me.
> - is integration with mach-o important?
> - is integration with PB/IB important?
I'm ignorant of these two, sorry.
> - do you think your answers to these questions might be radically
> different in a 8 months? a year?
That's always possible.
I'll also add a disclaimer - while I'm interested in Mozilla embedding,
currently we only do this for the Linux port of our product. We are not
actively porting to Mac OS, although I'm still trying to gain support
for that project.
> Here are the candidates:
>
> (1) MacOS9 only, not carbon, CFM.
> (2) Separate builds: MacOSX only Carbon CFM, MacOS9 only not
> (3) MacOS9 and OSX, Carbon CFM
In my naive opinion, option three would give the most bang for the buck.
> (4) MacOSX only, Carbon Mach-o with CodeWarrior
> (5) MacOSX only, Carbon Mach-o with gcc/make
