Em Quarta-feira 7. Abril 2010, às 20.13.32, ezjd escreveu: > 1) Some devices will have simple graphic module which doesn't support GL > (for cost reason at least). According to MeeGo goals (so ambitious one :-) > ), someone will want MeeGo to run on them sooner or later. If they have > to fundamentally change UI framework because of this, they will simply > forget about MeeGo. Technically, it wasn't easy to support UI w/ and w/o GL > in same UI framework, but the flexible Qt graphic system makes it feasible.
I don't doubt that there's a market for it, but the question at hand is
whether it's market we want to address. As Arjan said in his reply, it's not.
Without some kind of hardware acceleration, all the rendering and drawing has
to be executed on the CPU, with the implications that brings (power
consumption, hogging the CPU, bus bandwidth, etc.). You're only going to be
able to use the raster engine on low resolutions, and with little in terms of
animation-enhanced UIs.
Sure, ODMs could take the MeeGo core OS, remove the parts they don't want and
build their own UIs on top of that. But it's not something we as the MeeGo
community have to worry about.
(Also note that GL and GLES are not the only ways of accessing hardware
acceleration, but they are the only ways MeeGo is interested in supporting. Qt
also supports OpenVG)
--
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
