Hi, Is QtWebKit shipped with MeeGo 1.0 Netbook UX? If so it's part of the MeeGo API and will be loaded into memory the moment someone writes, say, a third-party Qt-based RSS reader.
Perhaps this is Markus' point? However, as Arjan points out this is more of an issue for the resource-constrained Mobile UX. There do seem to be two projects though: MeeGo Netbook (aka Moblin) and MeeGo Handset (aka Maemo); sharing a common core but with all UX and user-facing decisions being made separately. It'd be great to see more of the Netbook UX folk expressing concerns about memory footprint and developer consistency in the third-party space, even though it's less relevant to their target devices. Cheers, Andrew On 28/05/2010, Roger WANG <[email protected]> wrote: > Markus <[email protected]> writes: > >> Am Freitag 28 Mai 2010, 15:21:02 schrieb Roger WANG: >>> Markus <[email protected]> writes: >>> > Am Freitag 28 Mai 2010, 13:58:56 schrieb Roger WANG: >>> >> By that I mean that's not a valid question -- we don't load Chrome and >>> >> Fennec at the same time. >>> > >>> > WTF? I hever wrote that. >>> >>> "I don't get why on devices that have constrained memory anyway load two >>> web rendering engines into memory" ... >> >> Are you kindding me? Are you actually telling me that you work for Intel >> and >> are not able to understand basic English and recognize QtWebKit as >> rendering >> engine? > > Did you see any program in the release loading QtWebKit, or you just > post here before you actually get it running? > > -- > Roger WANG, Intel Open Source Technology Center > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > -- Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/ Maemo Community Council chair _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
