Em Sexta-feira 28 Maio 2010, às 13:15:40, Markus escreveu: > Am Freitag 28 Mai 2010, 13:08:31 schrieb Roger WANG: > > Markus <[email protected]> writes: > > > 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 > > > > We don't ship Fennec in MeeGo Netbook. > > Is this your entire answer? I asked why not a QtWebKit browser and you > answered "We don't ship Fennec"? > > According to the website Fennec is the confirmed browser for MeeGo Handheld > and Chrome if shipped for MeeGo Netbook. > Both are not QtWebKit browsers. Any my question was: Why?
I think the answer is quite simple: there are no good, productised QtWebKit-
based browsers yet.
Yes, there's Arora. And I'd love to see it as an option. But is it good enough
already?
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
