Embedding Mozilla in Mac OS X Cocoa Apps
JimCricket writes "Art & Logic has published a new article: Embedding Mozilla in Mac OS X Cocoa Apps . The author presents a detailed step-by-step guide for Mac OS X developers that want to use Mozilla within their applications."
the answer to your "question" is in the FIRST SENTANCE of the article.
Of course WebCore is JavaScript-enabled.
Or haven't you heard of JavaScriptCore? It's a part of WebCore.
Been a while since you checked out Safari, huh? iht.com, which was a pain in the ass for a long time, has been working for weeks now, since the late betas.
Safari ain't the bee's knees as far as I'm concerned, although I'm using it right now. It's got lots of advantages, sure, but it's still not handling as many pages as Mozilla for OSX. Mozilla 1.4 is fast and stable, and runs on almost everything. Safari is fast and stable and you need to be running OSX to use it.
Explorer is the world-wide de facto standard right now; it's a bad browser with a lot of propritary drek in it, and much more coming down the line, including possibly a subscription service. Why not embed Mozilla in everything? Since it's cross-platform, open source, and pretty good?
How would you rather do your online banking five years from now?
A) With Windows, which charges you $1,000 a month just for the right to use Explorer?
B) With Safari, which comes with a $25,000 entry-level iMac?
C) With Mozilla, which is free, and which will run on almost anything?
Mozilla isn't the be all and end all of browsers, but it's cross-platform, open-source, and runs all right. Nothing to sneeze at.
I noticed recently that there's work going on to embed SDL in Cocoa Apps, here's a link to some sample code:
5 54 35.html
"Mac OS X Cocoa Integration Patch and Sample Code"
http://www.libsdl.org/pipermail/sdl/2003-July/0
In theory, with this in place I believe it should also be possible to embed SDL in Mac OS X wxWindows apps, once the 'GetHandle' functionality is implemented there.
they explicitly said this at WWDC. Of course, the parent poster ignores the fact that they said they also run compatibility tests on all of the builds, including tests that are more stringent than some of the publicly available tests. I doubt they would break things with their "optimizations" as a result... a broken browser is worse than a slow one.