Hi Noemi,
I'll take a stab at this... though I'm not sure it's of more than historical interest as far as the Camino docs are concerned :-). Corrections/clarifications welcome.
On Nov 30, 2004, at 7:20 PM, Noemi Millman wrote:
Can someone please help me sort out the relationships between all of these? I've tried to RTFM (at http://www.mozilla.org/ports/fizzilla/ and http://www.mozilla.org/ports/fizzilla/Cocoazilla.html) but to no avail. But if someone can help me wrap my head around it, I'll write up a layman-friendly version to go into the new Camino Docs project.Correct. Think of Fizzilla as "Mozzilla suite for Mac OS X". CFM (Code Fragment Manager) is one of the two library managers available on Mac OS X. Its executable code is stored in the PEF format, and you'll sometimes hear the two terms exchanged a little loosely. The other library manager (which apple prefers, and calls "native") is dyld. dyld expects code and data to be stored in a format called Mach-O. CFM/PEF executables can be made to run on both classic Mac OS and OS X. dyld/Mach-O executables cannot. I'd be pretty surprised if this could even be built with anything newer than a Mozilla 1.3-ish source base; it's no longer maintained and requires the CodeWarrior toolchain to build.
Here's as far as I've gotten -- please correct me where I'm wrong:
- FizzillaCFM is simply a Carbonized version of what originated as the OS 9 version of Mozilla, that works on both OS 9 and OS X.
- FizzillaMach is described as "Carbon front-end, UNIX back-end, Mach-o based." I have to admit that I'm completely lost here. What parts is Carbon used for? Does the UNIX back-end refer to a version of Gecko written for UNIX, or pipelining or other application event handling written for UNIX? And Mach-O? I can't seem to get a good definition of it, let alone understand how it's used for this. ack!This is the "Mozilla suite for Mac OS X" that you can download today if you go grab the latest 1.7 release. (Since 1.2 or 1.3 I think?) Essentially, it refers to a Carbon GUI (meaning we use the Carbon API for drawing and handling user events), UNIX-style networking and file access, and a Mach-O format executable. I'd call FireFox for OS X a close relative of FizzillaMach.
- Cocoazilla.... I'm not clear what Cocoazilla is. Is it just the old name for CHBrowserView? Or is it something more, or something less, or something else?Strictly speaking, I'd say Cocoazilla is imaginary, or at least incomplete. If the cocoa widget and gfx libraries were completed and you built mozilla suite using them instead of the carbon stuff, I'd call that Cocoazilla. They're not, though; they're only complete enough at this stage to support CHBrowserView and Camino.
- CHBrowserView -- I gather this is basically Gecko wrapped in an extra layer so that it can be used sort of like an NSScrollView subclass and embedded into any Cocoa app? Or somewhat analagous to WebCore? It's not used for Fizzilla or Moz or FireFox, is it? In which case, Camino may currently be the only project using it, but there's no reason other Cocoa apps couldn't easily incorporate it.Correct. CHBrowserView is a subclass of NSView that wraps up gecko for embedding in a cocoa application. Occasionally on mozilla.org, you'll see CHBrowserView used to refer to the entire cocoa embedding module, which actually includes a bit more than that. Other projects could use it. I do not believe that the copy outside Camino's tree is actively maintained, however.
Hope this helps at least a little...
Geoff
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
