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

4 of 43 comments (clear)

  1. Link doesn't work ... by Anonymous Coward · · Score: 3, Informative

    ... as bugzilla have disabled referrals from Slashdot.

    Try this one instead, it routes via yahoo first:

    http://tinyurl.com/38uw

  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. Re:Handhelds? by Chexsum · · Score: 2, Informative

    You dont understand what theyre asking. The QT embedding widget needs to be ported or else itll be dropped from the distribution IIRC.

    The widget is like a wrapper for Gecko so that Gecko can be embedded into QT programs easilly. It probably wouldnt be too much work *if you were a C++ and/or QT programmer* to port it. =)

    Phoenix is a small and fast browser but I doubt its smaller and faster than a Gecko-based browser which doesnt use XUL *the Mozilla.org portable widget set* to render the layout. Check Galeon out sometime. :P

    --
    Pixels keep you awake!
  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.