[Development] Predefined platform dependent constants in QtQuick components

[Oleg Shparber]

Hi all,

During development of the QtQuick2 application for BlackBerry 10 I noticed
that all lists scrolls very quite slow. Same thing with any move of
Flickable's content. The reason is the high resolution of the device's
display.

The problem is that there are constants which predefine behaviour of
Flickable, PathView. Here's a short list of some of such #defines and
corresponding component properties:

Flickable:

   - QML_FLICK_OVERSHOOT
   - QML_FLICK_DEFAULTMAXVELOCITY
   - QML_FLICK_DEFAULTDECELERATION
   - QML_FLICK_OVERSHOOTFRICTION
   - QML_FLICK_MULTIFLICK_THRESHOLD
   - QML_FLICK_MULTIFLICK_RATIO
   - QML_FLICK_MULTIFLICK_MAXBOOST

PathView:

   - QML_FLICK_DEFAULTMAXVELOCITY

The actual documentation states that these properties are platform
dependent and that is not true now.

I think, that the right way is to move these parameters to the platform
plugins, so some platforms would be able to provide predefined constants
while others like BlackBerry, Android or iOS would calculate them depending
on device and display runtime information.

I am unsure about the implementation and maybe there are other thoughts on
this problem.

So, I would be happy to hear any ideas and would like to volunteer for the
implementation too.

Thanks,

Oleg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130129/11bd75d6/attachment.html>