Hi.
I searched a bit through the archives but didn't find any answers.
Can one please explain to me why Chrome and Firefox were chosen for MeeGo?
I don't get why on devices that have constrained memory anyway load two web 
rendering engines into memory: Chrome's WebKit or Mozilla's Gecko in addition 
to QtWebKit.
Not only are two rendering engines loaded all the time, Chrome and Fennec 
aren't even written in Qt. Chrome is written in Skia with some GTK widgets 
thrown in, while Fennec is written in XUL+Cairo with -- again -- some GTK 
thrown in.

>From my experience on the desktop, there is absolutely nothing wrong with 
QtWebKit. MeeGo Netbook could use a tweaked version of Arora for example and 
I'm pretty sure Nokia's Symbian and MeeGo teams could together release a fine 
QtWebKit-based browser for handhelds as well.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to