Resending, as I managed to confuse my gmail account. Sorry for the spam, Ville.

On 13 Jun 2011, at 22:30, Ville M. Vainio wrote:

> We all know and love Q_WS_MAEMO_5 and Q_OS_SYMBIAN for getting work done.
>
> However, as everybody ends up seeing,, there is no equivalent for meego.

What do you want it for? MeeGo is Linux, it isn't an operating system.

> Q_MEEGO_PROFILE  "tablet-reference"

Ah, I think get it, you want it for form factors. What are the Qt on
Android people supposed to do, sit out in the cold while you add MeeGo
specific code to a cross platform application development framework? I
don't really like that idea a lot. Nor does it fit too well with
anything that isn't specifically for mobiles.

However: I do agree there is a (cross platform) need for device
capability description. I think QSystemInfo would be a pretty good
home for things like this, seeing as it's already growing some similar
functionality.

I think that whatever grows, though, should probably look for specific
things they desire instead of generic things like 'tablet', because if
the past 5 years of technology have taught us anything, it is that the
devices of two years from now will probably look nothing like the
devices of yesterday.

So this might lead to things like (completely off the top of my head):

hasCapability(QSystemInfo::Touchscreen)
hasCapability(QSystemInfo::Mouse)
hasCapability(QSystemInfo::HardwareKeyboard)

...

(note that resolution, another popular candidate for things like this
is already available via QDesktopWidget, though I think in a Qt5
world, that should probably go to QSystemInfo too)
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to