Hi, this browser *engine* question was already touched upon many times here and it is certainly puzzling and deserves attention of those who are responsible for (architectural) decision making in this project (hopefully Intel team is reading this).
My *personal* impression (as someone who was directly involved in selection/customization/porting of browser engine in the past and also as former Nokian) is that Maemo (i.e. Nokia) browser team is build almost entirely of (russian speaking) people who *believe* that Mozilla/Gecko is the way to go and they do not care much about Acid3 test (100/100 achieved by WebKit and Opera on the same day - 26March2008, http://en.wikipedia.org/wiki/Acid3) or SunSpider tests (with screenshots forwarded to them) or other "signs" (Epiphany switched to WebKit, most successful devices like iPhone and Android use WebKit, etc, etc). Religious people are difficult to talk to, especially if they have no previous exposure to other philosophical systems (no smiles here). The end result - very poor browser performance on all Tablets (Loading objects, Loading objects, with complete freeze of UI), frustrated customers and ultimately the failure of the platform (since for most users browser is most popular application). To become a success a mobile stack needs to select best open source components and integrate them seamlessly and effectively on best platform (i.e. Debian) . LiMo is already doing this. Best regards, George Matveev --- On Tue, 3/23/10, Clint Christopher Cañada <[email protected]> wrote: From: Clint Christopher Cañada <[email protected]> Subject: Re: [MeeGo-dev] The nativer rendering model proposal in Fennec To: [email protected] Date: Tuesday, March 23, 2010, 10:23 PM Hello, Doesn't Qt's web component use webkit integration? Why doesn't Meego use that one, since the Meego UI Toolkit would be based on Qt as stated in the architecture layout? Nokia uses webkit on their symbian smartphones as well, so I do think that webkit would be a logical choice for a primary native browser - it would make Meego consistent throughout all platforms. Again, these are my thoughts on the matter. I do not mind though having a second browser as a choice. On 3/24/2010 1:56 AM, Arjan van de Ven wrote: > On 3/23/2010 10:41, Jeremiah Foster wrote: >> >> On Mar 23, 2010, at 3:48 PM, Arjan van de Ven wrote: >> >>> On 3/22/2010 22:53, Wu, Yong wrote: >>>> Background: >>>> Fennec uses a different rendering model as Firefox, >>> >>> I would be seriously concerned about using either Firefox or Fennec on a >>> mobile device. >> >> Fennec (or really Firefox Mobile) is popular, fast, and innovative. It is >> already available for the N900 which is a MeeGo platform. I don't share your >> concerns but I also don't think having to html rendering engines in MeeGo is >> necessary. >> > > yeah and if I'd have to pick one right now I'd pick webkit to be honest... > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
