Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mozilla/QT needs developers!

Posted by chrisd on from the zaurus-running-mozilla-would-be-cool dept.

strredwolf writes "They need developers to port Mozilla to TrollTech's QT. The origional port is since 0.9.9 and hasn't been updated since. We need that Mozilla for the iPAQ or Zaurus!!!"

6 of 43 comments (clear)

  1. Handhelds? by Xunker · · Score: 4, Interesting

    I have to question the actual feasability of Mozilla on a handheld.. well, current handhelds. Mozilla, while powerfull and efficient, is also monsterously huge in comparison to the miniscume persistant storage of handhelds and their small execution space.

    I''m sad to say that I think a 32 meg Zaurus couldn't run Mozilla well.. at least, not *stock* Mozilla.

    --
    Hilary Rosen's speech was about her love of money and her desire to roll around naked in a pile of money.
    1. Re:Handhelds? by DJayC · · Score: 4, Interesting

      Perhaps something more lightweight like Phoenix (or whatever they are going to call it)? But you are right, even Phoenix is a bit chunky for a handheld, but it's nice to know there are people who desire this. I think in order for a Mozilla based browser to work out it would have to be more than a "port".

  2. mozilla.org by Anonymous Coward · · Score: 5, Informative

    The last mozilla.org status update report covered this. It says that January 8, 2003 (scheduled release of Mozilla 1.3beta) will be the deadline to find an owner for the QT Mozilla port.

  3. Why not konqueror? by PinkX · · Score: 4, Interesting

    Konqueror has been out for ages already, it's lightweight, and free software. And Qt based.

    I don't know if it's tightly integrated into KDE to make it a Qt-only app (I guess it is), but just the browser component of it could be 'stripped out', KHTML is pretty mature. The AtheOS web browser is bassed off it.

    I am not a KDE/Qt developer nor a KDE user, so I might be wrong at this. But I think it would be easier to mantain a stripped-down, kde-less version of the browser component of Konqueror instead of trying to keep up-to-date with a Qt port of Mozilla, which BTW is a bit bloated for PDAs (and please don't get me wrong here, I *LOVE* Mozilla).

    --
    Articulos para gente geek: Poleras, linux, libros y mas
    1. Re:Why not konqueror? by Jagasian · · Score: 4, Interesting

      I am a big KDE fan and KDE user. I used to think Konq was the best browser for Linux, and it truely was... until Mozilla 1.0. Yes, for years I swore that Mozilla was going nowhere, but once 1.0 was released, and I could see how stable it was... how well it rendered sites. It was then that I realized that Mozilla did it.

      Netscape is back! It reminds me of that Obi-wan quote:
      "You can't win, Darth. If you strike me down, I shall become more powerful than you could possibly imagine."

      How is Netscape more powerful than ever? Well technology wise, functionality wise, and performance wise, it matches Internet Explorer... but what truely makes it invincible is that it is open source software. Just like Obi-wan returned from the grave so has Netscape.

  4. What a widget port of Mozilla is. by dbaron · · Score: 4, Informative

    No, it's not just an embedding widget. A port of Mozilla to a toolkit is code that maps the interface Mozilla uses for interacting with native widgets and event queues (the part in widget/src/qt/) and graphics devices (the part in gfx/src/qt/) to the particular toolkit's API.

    The default Unix port of Mozilla uses GTK+. (It's the default in the build system for platforms other than Windows, Mac, OS/2, BeOS, and QNX, and it's the one distributed in mozilla.org release builds for all but those platforms.) This means that many of the interactions between Mozilla and Xlib have GTK code in the middle. (Not all of them do -- some parts of the code, such as the font code, uses Xlib APIs directly, although the Xft builds use Xft2 and fontconfig APIs instead.) It also means Mozilla gets a good bit of look-and-feel information from GTK themes (more recently than it used to).

    In addition to the GTK+ port, there are also a raw Xlib port (no toolkit between Mozilla and Xlib) and a QT port, but the QT port is poorly maintained and will be removed if no maintainer steps up (as the Motif port was a while ago).

    Some of the ports also come with embedding widgets that allow embedding of the layout engine into programs using those toolkits. However, the embedding widget is just a small and optional part of the port. I also don't see any reason that it wouldn't be possible to use a QT embedding widget for Mozilla even if Mozilla is using GTK+ internally.