[Development] Qt5 missing features
lincoln.ramsay at nokia.com
Thu Apr 12 05:44:53 CEST 2012
On 04/12/2012 01:20 PM, Alan Alpert wrote:
>> If there was a "standard API" defined for a "components" and each
>> platform provided something that was source-compatible with this API
>> then that would work too (without indirection) but I haven't seen anyone
>> suggesting that a platform's "components" should adhere to some
>> "standard API".
> I suggest it :) . It's a de-facto standard already if you can simply comment
> in the appropriate import.
Well... I don't know if you can actually do that.
> This doesn't require a theme manager abstraction. It could be handled with a
> Widgets import that resolves to MeeGoWidget,SymbianWidgets or DesktopWidgets
> based on runtime platform.
There's no need to resolve anything, just build the Widgets import using
different code depending on the platform you're building for. Code could
be shared or not as appropriate.
I suppose you'd also need some kind of test suite that validated the
source-compatible promise of this Widgets import.
Nothing I've heard about QML Components work has led me to believe a
source-compatible, cross-platform API is what is being created.
"The API is mostly aligned with our ongoing mobile SDK effort, but I
also had to create some uniquely desktop-related widgets such as
ScrollBar, ScrollArea and TabFrame."
Because I'm lazy, I won't be investing any effort into learning a QML
API that only works on 1 platform.
Lincoln Ramsay - Senior Software Engineer
Qt Development Frameworks, Nokia - http://qt.nokia.com/
More information about the Development