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?
- is being able to build with free tools important?
- is integration with mach-o important?
- is integration with PB/IB important?
- do you think your answers to these questions might be radically
different in a 8 months? a year?
Here are the candidates:
(1) MacOS9 only, not carbon, CFM.
This is pretty much what we have today. Some people may not care about
OSX at all. Requires the Metrowerks tools.
(2) Separate builds: MacOSX only Carbon CFM, MacOS9 only not carbon CFM.
This is similar to the tack we are taking with the mainline Navigator
application: two separate builds, one for carbon and one not. The carbon
build is only qualified on MacOSX, the other is only qualified on
MacOS9. Requires the Metrowerks tools.
(3) MacOS9 and OSX, Carbon CFM
One build, one embedding strategy. If you want to embed us, your app
needs to be Carbon and be built using the Metrowerks tools.
(4) MacOSX only, Carbon Mach-o with CodeWarrior
Something we have yet to explore, but now more possible with the
improved mach-o linkers from Metrowerks. Your app would run on OSX only
and be mach-o based. Obviously requires the Metrowerks tools.
(5) MacOSX only, Carbon Mach-o with gcc/make
Our makefile-based mach-o build of Fizzilla is slowly coming online. The
ultimate goal is to be able to integrate an embedded mozilla into
ProjectBuilder/InterfaceBuilder. All required tools ship with OSX (read:
free).
Confused yet? I sure as heck am.
--
Mike Pinkerton
Mac Browser Weenie
[EMAIL PROTECTED] http://people.netscape.com/pinkerton
