Mozilla/QT needs developers!
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!!!"
← Back to Stories (view on slashdot.org)
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.
... as bugzilla have disabled referrals from Slashdot.
Try this one instead, it routes via yahoo first:
http://tinyurl.com/38uw
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.
But as I see it, having it work with QT is important because it makes things possible for sub-projects of mozilla (some of which are more aimed into pda/embedded market) and also because having support for it further developed (and not removed from the source tree) might provide many important pieces of code which can be utilized in other open source projects as well... I think QT is very interesting concept from the embedded devices point of view, especially... I don't know but I think this might be rather important from a wider view also :)
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
Mozilla's performance is barely acceptable on my humble 500MHz K6-2. It stinks on UltraSPARC. I suspect it stinks on anything that isn't x86, partly because of GCC's inefficiency on non-x86 architectures. Therefore I hate to think what it would be like on a 206MHz StrongARM. I think Mozilla needs a lot of optimization before anyone can contemplate running it on a handheld. On a related note, why is Netscape 7 so much faster than Mozilla on the same machine? I know an ipaq user who runs dillo for his web browser. It seems far better suited to hand-held use.
Stick Men
This is the way the free market/software system works, there will always be dead/dying projects. The time to allocate to such projects is a valuable resource, obviously people have chosen to invest it in something else.
If someone found it important enough, they would find the time themselves, or come up with money to hire someone else to do it.
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.
Or it'll be removed (like the Motif one was)
Ask and ye shall receive.
"I assumed blithely that there were no elves out there in the darkness"