Hi, On Mon, Jan 31, 2011 at 10:59 AM, <jan-arve.saet...@nokia.com> wrote: > > So you would prefer that we did not do any effort to 'hide' the API that > is not common, since that would enable 'qml developers' to use just one > 'import Qt.labs.components.native', and utilize the platform-specific APIs > when needed? (Of course they might still have to use platform-specific QML > files (but still with 'import Qt.labs.components.native'), but I don't see > how native imports will solve that. (It's a different problem, really).
Just today we were discussing about this again, this time with Thiago Santos. He made me realize that perhaps MeeGo/Symbian/Xxx specific imports make sense for more or less highly platform specific components, perhaps ToolBar/StatusBar for instance. But still, in my opinion, the common components should be imported from the common Qt.labs.components or whatever namespace. Hopefully that would motivate applications to stay cross-platform wherever possible, if we didn't provide any platform specific extensions to simple widget type components. So I'm rather proposing that the whole native imports thing shouldn't even exist... - import Qt.labs.components (common components with common api and nothing else. can be still implemented separately for various platforms/styles if reasonable, but would be nice to at least share the code as much as possible) - import com.meego (MeeGo specific components only, those handling the platform integration etc.) - import com.nokia.symbian (similarly Symbian specific components only) PS. What's up with the mailing list? I'm missing some emails every now and then. For example Jan-Arve's latest reply did not reach my Nokia account at all. -- J-P Nurmi _______________________________________________ Qt-components mailing list Qt-components@qt.nokia.com http://lists.qt.nokia.com/mailman/listinfo/qt-components
