Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Mozilla Businesses Programming The Internet Apple IT Technology

Embedding Mozilla in Mac OS X Cocoa Apps 49

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."
This discussion has been archived. No new comments can be posted.

Embedding Mozilla in Mac OS X Cocoa Apps

Comments Filter:
  • by foyle ( 467523 ) on Tuesday July 22, 2003 @02:49PM (#6502226)
    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 [apple.com]
    • I'll be happier about KHTML when it can read www.iht.com. Mozilla really is about the best out there when it comes to page rendering, folks.
      • by Anonymous Coward on Tuesday July 22, 2003 @04:00PM (#6503286)
        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.
    • I just moved from being a Slashdot reader to someone with a username and password JUST so I could say exactly that.... turns out you more than easily beat me to it, though. LOL Mozilla is one of the last things I would want to be embedding into an application I write.
    • by Anonymous Coward
      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. Wh
    • The only reason I can think of is for visual HTML editors. They could embed both frameworks for previewing pages without having to load a separate browser.
    • Gecko/Moz has a lot more features. We embed IE in an app here at work because it has features we need. It's possible we might move to Gecko/Moz in the future, but KHTML is out of the question - we need things like in place editing, simple licensing, and behaviours/XBL.
  • Could this be done with Web Core as well? I assume it could be. What advantages would Gecko/Moz have over it? I don't really understand much of the technical mumbo jumbo in the article so any enlightenment would be great.

    It seems that the basic use for this would be to simply provide app support for all the basic web standards, but what other uses could it have?
  • by Tumbleweed ( 3706 ) on Tuesday July 22, 2003 @02:56PM (#6502280)
    I don't even wanna know why you'd want to embed the whole frickin' browser in anything, rather than just the renderer. And if you're going to embed the renderer, then just use the system one in WebCore, based on the KHTML renderer.
    • READ THE ARTICLE (Score:2, Informative)

      by Anonymous Coward
      the answer to your "question" is in the FIRST SENTANCE of the article.
    • by Quixotic Raindrop ( 443129 ) on Tuesday July 22, 2003 @03:10PM (#6502411) Journal
      Actually, one reason _not_ to use WebCore is that it doesn't handle quite a number of websites using authentication now, which tells me that their authent package is broken (or, simply behind). IIRC, Safari uses webcore, and has tremendous difficulty (even yet) with e-commerce and online banking sites. Mozilla/Mac OS X is able to connect to these sites, and I assume would be a better choice for secure connections (whether Gecko or Mozilla itself).
      • The site also mentioned a question as to whether WebCore is javascript-enabled, and I must say, I don't know the answer to that question, either.
      • Quixotic Raindrop wrote:

        Safari uses webcore, and has tremendous difficulty (even yet) with e-commerce and online banking sites.

        I use Safari all day every day, including for online banking and plenty of ecommerce, and I don't have any consistent problems.

        Furthermore, using the CocoaDev One Line Browser [cocoadevcentral.com], I was able to login to my bank site and view my pending bill payments (https) as well as login to a site which uses HTTP basic auth without writing a single line of extra code.

        What are these problems you

        • I have entered several bugs with Safari regarding online banking or other authentication. For example, Safari does not correctly handle logging into thinkgeek.com. I don't trust you enough to tell you what banks I have accounts with, but there are at least five with which I can do business in either IE 5.2 or Mozilla, but cannot if I use Safari.
        • My example: I can't log on to my school's wireless network with Safari (via https). I have to use Camino or Moz.

          Why? Beats me. But it's true. With Safari 1.0.
          • I certainly didn't mean to suggest that Safari was incapable of bugginess.

            In your case, do you have the security preference "accept cookies" set to "only from sites you navigate to"? I've found that that setting doesn't play well with single-sign-on type systems where you (sometimes invisibly) bounce around from the initial server you visit to an auth server and back.

            Then again, I have also found that Safari has some problem with regular cookies set by the SnipSnap [snipsnap.org] blog/wiki application (ultimately set b
    • by megabulk3000 ( 305530 ) on Tuesday July 22, 2003 @03:52PM (#6503157) Homepage
      Sure, check this article [cocoadevcentral.com] 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!)
  • by xyrw ( 609810 )
    I read the article, but don't understand why it would be necessary to embed a whole browser. Why not just the rendering engine? Wouldn't embedding Mozilla create a lot of overhead?
  • Why embed all of Mozilla? I'm positive that for most of these apps, all that would be needed is Firebird...
  • by Steveftoth ( 78419 ) on Tuesday July 22, 2003 @06:21PM (#6505353) Homepage
    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.
  • by follower-fillet ( 140975 ) on Wednesday July 23, 2003 @05:45AM (#6509690) Journal
    I noticed recently that there's work going on to embed SDL in Cocoa Apps, here's a link to some sample code:

    "Mac OS X Cocoa Integration Patch and Sample Code"

    http://www.libsdl.org/pipermail/sdl/2003-July/05 54 35.html

    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.
  • Camino (Score:3, Insightful)

    by mbbac ( 568880 ) on Wednesday July 23, 2003 @10:56AM (#6511352)
    That's kind of the whole point of the Camino Project [mozilla.org]. Why reinvent the wheel?

"Why can't we ever attempt to solve a problem in this country without having a 'War' on it?" -- Rich Thomson, talk.politics.misc

Working...