On Sat, Feb 12, 2011 at 08:30, Zhu, Peter J <[email protected]> wrote:
> [Carsten wrote:]
>> I think the aim isn't for this to be a MeeGo API, but for a platform
>> feature for components in hardware adaptation to distinguish between
>> devices where it's needed. Those components would then be able to read
>> /etc/boardname which was initialised by system startup.
>
> Ok.
>
> We might consider having a such API since MeeGo is targeting multiple
> categories of devices.
The discussions around *that* API (in Qt) are at a different level,
though. Whether you're x86 or ARM, or Moorestown or OMAP3, doesn't
tell you whether or not you have a keyboard; touchscreen; display size
or preferred size of applications and interactions.
The latter is more capabilities oriented which should also have an
abstraction down to match one of the UXes (i.e. "I'm Handset", "I'm
Netbook", "I'm IVI") and possibly even some policy ("Be fullscreen",
"Use large icons", ...). It's this API, not the boardname one, which
should be a MeeGo API, IMHO.
Cheers,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
Maemo Community Council member
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
