On Mon, Jun 13, 2011 at 23:27, Attila Csipa <[email protected]> wrote:
> On Tuesday 14 June 2011 00:56:08 you wrote:
>> 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.
>
> It doesn't matter if it's an OS or not. Whatever it is, it has
> *compliancy specifications*. It means that stuff HAS to be done in a
> certain way. No amount of feature-detection will tell you the required
> naming schemes, dependency rules and such.
Absolutely, there are three use cases, only one of which should be
reported from within Qt itself:
1) Feature detection. Includes screen sizes, orientation default etc.
2) Build time. As Attila says, paths & icons may need to be different
for different platforms.
3) API availability. "Raw" QML can have an Item as the root item,
however MeeGo UX Components and Qt Quick Components have their own
"window" items which should (must?) be the root; and have different
import statements.
As a developer, I want to write a Qt Quick app which can run on Maemo,
Harmattan, Symbian, MeeGo and Android; and currently that seems overly
difficult.
Cheers,
Andrew
--
Andrew Flegg -- mailto:[email protected] | http://www.bleb.org/
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
