Sure, let me try. SCROLL BARS: I think this is just a question of time and we will all just use scroll indicators. Also we could make it possible to do native scrollbars using the flickable with some effort, like to make sure that the relayout does not cause a resize event.
SELECTION: Selection is hard and we will have to find out how we want to do this in a mouse/touch environment SCROLLING: Not allow mouse to actually cause panning. ADDITIONAL FEATURES: Changing mouse cursors etc, maybe pressed mouse wheel panning (as they support on windows) html forms using native look frame flattening? frameset? Kenneth >> There is a lot of things that would need to be fixed for the touch-interface >> before we can dump the idea of a separate desktop mode. > > Can you list out some of the things that would need to be fixed/reasons for > keeping a desktop mode around? > > If we don't do it now, I think it won't ever get done. > > BTW Simon -- I agree to just about every one of your points. > > ~Keith > -- > Keith "Keithel" Kyzivat | mailto: keith.kyzi...@nokia.com > Senior SW Engineer, Browser | callto: +1 (978) 821-7115 > Nokia, MP Development | sendto: 5 Wayside Rd. > | Burlington, MA 01803 USA > _______________________________________________ > webkit-qt mailing list > webkit-qt@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt -- Kenneth Rohde Christiansen Senior Engineer Nokia Mobile Phones, Browser / WebKit team Phone +45 4093 0598 / E-mail kenneth at webkit.org http://codeposts.blogspot.com ﹆﹆﹆ _______________________________________________ webkit-qt mailing list webkit-qt@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt