On Wed, Sep 21, 2011 at 1:15 PM, Adriano Rezende < [email protected]> wrote:
> On Wed, Sep 21, 2011 at 9:56 AM, <[email protected]> wrote: > >> > 1 - platform specific qml widgets (I don't care if technically the >> > desktop widgets share the same implementation and use the QStyle API >> > to draw them the way they should be - that's actually a good way to >> > go); >> > 2 - The "Qt set" (that ideally would be qt's default offer - that >> > works on all the platforms, enabling us to write applications that >> > would behave and look like the same on all platforms). >> >> I suspect Metro and the Qt set are two rather different things. Metro >> seems to belong more in category with IOS and Android components than >> desktop but I have yet to try a Metro enabled application… >> >> The QtDesktop components will most likely map to the traditional windows >> apps. However even within the Qt Desktop components, I think we will have to >> add a set of platform specific widgets such as SearchEdit on the mac etc. >> > > I agree. We need to have two different widget sets, one for desktop and > another one for mobile. The desktop widgets would basically mimic the old > QWidget behavior regarding styling and common properties; it would have good > integration with any platform if using internally the QStyle machinery > (maybe with some improvements? :)). Also, we would need to provide real > layout, with minimumSize and maximumSize properties, for the desktop widget > set or add this support in QML. > Looking at the qt-components repo it seems quite mature the desktop components. Is there a roadmap in some place? Regards, Adriano
_______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
