On Thu, 3 Mar 2011 16:43:45 +0100
<henrik.ha...@nokia.com> wrote:
> Hi,
>
> After some internal discussions, we're wondering the best approach
> for making a cross-platform API for Qt Quick components. A bit of
> background; currently, we have a common API that we use an apichecker
> test to verify conformance - and we're quite OK there. However, there
> are a few properties and features that are platform specific - for
> instance 'focusable' on MeeGo's ImplicitSizeItem, needed for some
> specific item interaction features, or Symbian having 'title' in it's
> Page.
>
> The convention we have used so far is;
> * '__' is private and should not be used. Best approach is to have
> a QtObject {id:property} with properties for hiding private properties
> * '_' is platform specific, and should be used with care..
>
> however, neither of these illustrate which platform you are locking
> yourself to - and it does not allow encapsulating the platform
> specific property for e.g. Symbian.
>
> Question to the list; are there better techniques for exposing
> properties to a common element from a specific implementation - and
> be able to use such properties in the implementation effectively? Can
> attached properties be used for this without breaking the ability to
> deploy the App to a different platform that doesn't have this
> property?
>
> Others, please pipe up if I forgot some details about our discussion.
>
An important point that is related: an application really should be
able to determine what type of display it is currently using.
Whether it is pocket-size or theater size. Fixed size or projected.
Whether it has touch or doesn't.
These things allow the application to decide what to do, either
statically or dynamically.
And please note, it is the display currently in use for the application
that matters, not the display normally attached to the device it is
running on.
The display characteristics can vary with the use of attached
projectors, or docking stations for mobiles, or remote logins. WIthout
knowledge of display characteristics, applications have no hope of
dealing with any of this.
Cheers,
Bernd
--
Bernd Stramm
bernd.str...@gmail.com
_______________________________________________
Qt-components mailing list
Qt-components@qt.nokia.com
http://lists.qt.nokia.com/mailman/listinfo/qt-components
