On Thu, Nov 10, 2011 at 6:35 PM, <[email protected]> wrote: > Hi, > > I think we can eliminate this boolean altogether. Why don't we always have > the interaction engine > around (might be nice to get it working on desktop computers with an attached > touch screen)? > It should act only on touch events.
That could be fine. > > One remaining point is the resizeToContents behaviour, which in turn will > toggle whether to show > scrollbars or indicators (missing atm). A preference no? I don't think here we increase the complexity like we had in WK1. > > 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". That could be easily enabled/disabled through a private thing. > > 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. Sounds like magic to me. > > 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". Well the merge was a good step, let's figure out the two remaining issues :D. > > Simon > _______________________________________________ > webkit-qt mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt > -- Alexis Menard (darktears) Software Engineer INdT Recife Brazil _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
