Hi there,<br><br>Analizing the hildon widget that people want to have in Qt, I can say that:<br><span class="clickable" onclick="dr4sdgryt(event,"Ox")"><span class="sg"><span class="se1"><span class="trn">There are "hildon/ized" widgets that will be part of Qt itself and Qt hildon widgets that will come from a different lib (not implemented yet).<br>
Some "essential" widgets like </span></span></span></span>Hildon stackable windows and Maemo5 menus will be part of Qt GUI module.<br>They have been already coded and the code is in our git repository.<br><br>Qt is able to use Hildon Native dialogs (eg: File dialogs). We can support others Hildon dialogs just adding a couple of<br>
lines in the style.<br><br>The rest of hildon widgets that won't be part of Qt itself and they will be part of another project that me, David and maybe other people interested in<br>can do togheter.<br><br>Ciao,<br>Antonio<br>
<br><br><br><div class="gmail_quote">
On Mon, Sep 7, 2009 at 11:06 AM, David Greaves <span dir="ltr"><<a href="mailto:david@dgreaves.com" target="_blank">david@dgreaves.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><a href="mailto:Karoliina.T.Salminen@nokia.com" target="_blank">Karoliina.T.Salminen@nokia.com</a> wrote:<br>
</div><div>>> If you have custom widgets in every program on a system, users will find<br>
>> it harder to use. They will not know what to expect when they tap on a<br>
>> widget they never saw before... that's the point of having guidelines.<br>
><br>
> Please read my sentences above. I meant about replicating the functionality of the widget<br>
> done with other technology with another and ending up with exactly the same user experience.<br>
> It is possible and the guidelines can be followed to create the new widgets.<br>
> There is nothing that prevents that, it is just some additional work required for the developer<br>
> as there are hildon widgets lacking from the selection of widgets on the Qt side.<br>
</div>Agreed.<br>
I've asked Antontio to start a project so we can create a set of hildon-widgets.<br>
<br>
What would be good would be some collaboration on creating a prioritised list<br>
and documenting the required behaviour.<br>
<br>
<a href="http://wiki.maemo.org/Qt4_Hildon#Where_are_the_Hildon_Widgets_for_Qt" target="_blank">http://wiki.maemo.org/Qt4_Hildon#Where_are_the_Hildon_Widgets_for_Qt</a><br>
<a href="http://wiki.maemo.org/Qt4_Hildon/Qt_Hildon_Widgets" target="_blank">http://wiki.maemo.org/Qt4_Hildon/Qt_Hildon_Widgets</a><br>
<div><br>
> If you compare the kinetic scroll list on the startup wizard to the kinetic scroll list elsewhere,<br>
> you may find that it functions the same way, despite that is Clutter and elsewhere it is Gtk.<br>
> Similarly I am sure it can be done also with the Qt in the same way, so that as end user you can't see the difference<br>
> (except that on different toolkits there may be slight performance differences, e.g. pure clutter<br>
> can be obviously faster than Gtk and similarly the performance may differ on the Qt version to direction or another<br>
> depending on the case).<br>
><br>
> It just requires accurate tuning for all the parameters to get the scroll behavior exactly the same and<br>
</div><snip><br>
<div><br>
> What comes to the kinetic scroll list, it has certain little details that are important, otherwise it will feel different (and not right):<br>
> - edge bounce<br>
> - easing on edge bounce (the movement decelerates before it stops instead of stopping mechanically)<br>
> - friction<br>
> - inertia<br>
> - scrolling speed (comes from the physics of the friction, inertia, and the initial speed given by the finger)<br>
> - finger following<br>
> - item selection sensitivity from touch<br>
> - item deselection sensitivity from following movement<br>
> - stoppable movement (despite of high inertia, stopped finger stops the movement immediately)<br>
><br>
> To get these right, it really requires trying out on the device how it feels. When doing the startup wizard we found that<br>
> some sensitivities (e.g. selection sensitivity) need to be a bit different when operated on mouse than when operated on finger on the device.<br>
</div>I (and others) wrote the Qt fingerscroll that we have (had?) in experimental.<br>
All those factors are parameters.<br>
It also works on any scroll-based widget 'for free' and allows highlighting and<br>
drag'n'drop.<br>
I completely agree that it needs tuning on the device... sadly I don't have<br>
one... but if someone wants to send me one...<br>
<div><br>
> Once the list is perfected, all the other widgets are easily composited from these lists and other widgets.<br>
> So it is a good idea to start from making a list on Qt to function exactly like it functions on the Hildon.<br>
</div>I've asked Antontio to start a project so we can create a set of hildon-widgets.<br>
<br>
IIRC we also need to do dbus integration too.<br>
<div><br>
David<br>
<br>
<br>
--<br>
"Don't worry, you'll be fine; I saw it work in a cartoon once..."<br>
</div><div><div></div><div>_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org" target="_blank">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><br><a href="http://www.brainyquote.com/quotes/authors/m/mike_ditka.html" target="_blank">Mike Ditka</a> - "If God had wanted man to play soccer, he wouldn't have given us arms."