Slashdot Mirror

← Back to Stories (view on slashdot.org)

Embedding Mozilla in Mac OS X Cocoa Apps

Posted by pudge on from the mmmmm-ozilla dept.

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."

6 of 49 comments (clear)

  1. Why not WebKit/KHTML? by foyle · · Score: 5, Insightful

    Why would you embed Mozilla, which is acknowledged to be bloated even by its supporters, instead of Apple's WebKit (based on KHTML, used in Safari)?

    WebKit Docs

    1. Re:Why not WebKit/KHTML? by Anonymous Coward · · Score: 4, Informative

      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.

  2. Re:embed _Mozilla_, or Gecko? by nitehorse · · Score: 4, Informative

    Of course WebCore is JavaScript-enabled.

    Or haven't you heard of JavaScriptCore? It's a part of WebCore.

  3. Re:embed _Mozilla_, or Gecko? by megabulk3000 · · Score: 5, Interesting

    Sure, check this article for instructions on how to make a one-line-of-code web browser in Cocoa using WebCore (and the comment at the bottom of the article which tells how to make a no-line-of-code browser!)

  4. Silly unless you want to make your own browser.. by Steveftoth · · Score: 4, Insightful

    For most programmers, we are just looking for a way to embed a small HTML rendering system so that we can display documentation, help, or someother hyperlinked document. Quickly too, so that we can easily get back to making a quality application. Gecko is a huge project and if you want to use it as the basis for an application more power to ya.

    However, Apple has the edge here with WebCore, you can now make a generic web browser without a single line of C/C++/ObjC code. Using only project builder, Interface Builder and WebCore, you can create a custom browser. It won't have many options, but it's quick and easy. Takes like 10 minutes to get working if you have all the tools installed.

  5. Re:the point is this... by madamimadam · · Score: 5, Interesting

    You seem to be forgetting the VITAL point that Apple REFUSES to release a new version of Safari, and therefore the WebKit, if it is at ALL slower that the previous version. This is a definate fact that Apple hangs on to dearly and could be why there are still a few places that they need touching. As per WWDC, sometimes coders kind of cheat by optimising another part of the code so that their new code does not slow down the browser but as long as the end result is that the new build runs at least as fast as the previous build, Apple will release it. If it is at all slower than the previous build, Apple refuses to let it out of the closet.