Hi,
On 03/05/11 13:41, Tom Swindell wrote:
<snip>
I think from my perspective, I'd probably be writing several QML UXs
for my apps anyway, one for tablets (large screen) and another for
handsets, the main reason being, though a perfect UX designed in QML
could be scalable across all screen dimensions. Separating the paradigms
into seperate QML UX profiles is just a lot simpler and probably a lot
less of a time investment.
<snip>
I'm not disagreeing with that at all. Having the *freedom* to do what
you want with UI is a great thing, and I'd never discourage that.
Likewise, I don't even discourage different *look and feel* for
components between devices, device categories, or vendors.
What I do worry about is different *API* for that look and feel. It's
basically taking compliance and throwing it out the window, in a very
subtle manner. You're still using Qt, so you're technically compliant,
but by bringing your own common API to the party, you're basically
locking out someone putting an application on your device and running
it, which, as I understood, was the very point of things like the
compliance program.
But yeah .. Very confusing :(
And that :)
(FWIW, I have so far been doing my own interfaces, too, mostly because I
don't develop on MeeGo, and thus, can't use MeeGo's components...)
--
Robin Burchell
http://rburchell.com
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines
