[webkit-qt] on QQWVP::initializeDesktop and ::initializeTouch and d->useTraditionalDesktopBehaviour

Alexis Menard alexis.menard at openbossa.org
Thu Nov 10 15:04:01 PST 2011


On Thu, Nov 10, 2011 at 7:57 PM, Kenneth Rohde Christiansen
<kenneth.christiansen at gmail.com> wrote:
> I think we should always use resizeToContents (except for the testing
> system) and then do what is needed to make it rock on the desktop as
> well:
>
> a) add wheel support
> b) fix the viewport meta handling
> c) draw scrollbars/indicators using a separate layer

https://bugs.webkit.org/show_bug.cgi?id=72064

waiting for review :D.

> d) implement fixed position using layers
> e) ...
>
> Safari on Lion also showed us that hacking in pinch/double-tap to zoom
> in WebCore just results in lots of bugs for no obvious gain.
>
> We don't need to do this now, but it should be the target.
>
> Cheers,
> Kenneth
>
> On Thu, Nov 10, 2011 at 11:39 PM, Keith Kyzivat <keith.kyzivat at nokia.com> wrote:
>> On 11/10/2011 04:35 PM, ext simon.hausmann at nokia.com wrote:
>>>
>>> One remaining point is the resizeToContents behaviour, which in turn will
>>> toggle whether to show
>>> scrollbars or indicators (missing atm).
>>>
>>> We clearly need a way to forcibly enable/disable resizeToContents, at
>>> least for WTR. But ideally
>>> we're smart about it and we just initialize it "correctly".
>>>
>>> We could play with heuristics, such as looking at the screen resolution
>>> and the dpi (QGuiApplication::primaryScreen()).
>>> If the physical dimension of the "display" is below a certain shreshold
>>> (10"?), we simply figure that
>>> scrollbars don't make sense and go to resizeToContents mode.
>>
>> I had mentioned something like that here months ago to distinguish this.
>>  Seems logical, and I think it's the right way to go.  If the physical size
>> of the device is below some threshold, I think it does follow suit that
>> you'll not want traditional scrollbars.
>>
>> Now -- do you do so by thresholding the length and width (if height < x or
>> height < width, don't show scrollbars), or do you do it by area (if device
>> area is < x, don't show scrollbars)?
>>
>>> Anyway, I think you get what I'm getting at: Let's see if there's a way to
>>> avoid a mode/boolean
>>> that distinguishes between "desktop" and "mobile".
>>
>> _______________________________________________
>> webkit-qt mailing list
>> webkit-qt at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>>
>
>
>
> --
> Kenneth Rohde Christiansen
> Senior Engineer
> Application and Service Frameworks, Nokia Danmark A/S
> Phone  +45 4093 0598 / E-mail kenneth.christiansen at gmail.com
>
> http://codeposts.blogspot.com ﹆﹆﹆
> _______________________________________________
> webkit-qt mailing list
> webkit-qt at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
>



-- 
Alexis Menard (darktears)
Software Engineer
INdT Recife Brazil


More information about the webkit-qt mailing list