In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote:
> Then we could work on replacing gfx with quartz or cocoa calls. Direct > quartz might map better to the gfx apis. Direct Quartz is likely the way to go from the performance point of view. Isn't it so that the same direct Quartz code can be used both in Fizzilla and in a Cocoa port? > None of this really impacts networking or layout as gfx/widget have been > fairly well abstracted from the rest of the app. We've actually done a > reasonable job of isolating native call sites. What should I read in order to understand events, concurrency and threading in Mozilla and in Cocoa? > The one problem is plugins. Since they assume Carbon, we have to have a > way to meld the carbon and cocoa event and drawing together within the > same content area. Omniweb does this by creating a Carbon window and > hacking a NSWindow around it. This kinda makes going the full cocoa > route sorta pointless, no? Being able to embed in a Cocoa app and being able to create a counterpart of Galeon and K-Meleon for Mac OS X is important. It would be a shame if the plug-ins were the show-stopper. The three plug-ins that most people "need" are: QuickTime, Flash and the iTools plug-in. For me, the ability to extract the URL of a QuickTime movie and asking QuickTime Player to handle it would be sufficient. I know that other people prefer to have everything in the browser, but I think implementing the QuickTime functionality as a plug-in is a huge overkill. Cocoa apps can display QuickTime movies. The need to support the QuickTime plug-in would be eliminated if the Cocoa port of Mozilla called QuickTime itself. The source for handling Flash is available. Would it make sense to expect someone to produce a Cocoa-port-compatible Flash plug-in as a Carbon-free XPCOM component? It is very uncool that Mac userness is communicated to iTools by using a plug-in. I'm not too optimistic about Apple switching to a better approach. Anyway, given the choice between FizzillaCFM with the iTools plug-in and a browser with a Cocoa-based native Aqua UI and Gecko as the layout engine but without the iTools plug-in, I'd choose the latter as my everyday browser. -- Henri Sivonen [EMAIL PROTECTED] http://www.clinet.fi/~henris/
