On Friday, October 07, 2011 10:37:31 AM ext Andreas Kling wrote: > On Fri, Oct 7, 2011 at 9:46 AM, Simon Hausmann > <[email protected]>wrote: > > > On Friday, October 07, 2011 02:20:00 AM Aharon Yael (Nokia-MP/Boston) > > wrote: > > > QTouchWebPage is nothing like QWebPage or QWKPage. > > > To me, it is very confusing that it has "page" in its name. > > > I would rename it to something that reflects better what it really is. > > > > The name QTouchWebPage is not intended to be visible in the QML API. The > > only > > thing visible of it are its properties/signals/slots as part of the page > > group property: > > > > TouchWebView { > > id: webView; > > } > > > > TextInput { > > > > Keys.onEnterPressed: { > > webView.page.load(text); > > } > > } > > > > Would you like for the page property to disappear altogether and instead > > prefer the functionality > > to be merged into the view? > > > > > IIUC we need to expose the item inside the clipping viewport somehow if we > want to support anchoring e.g a gutter to the page item.
Ah yes, you're right. That was one of the main arguments in favour of a page item - The QML reflects the visual hierarchy. > I'd also argue that the QWKPage name didn't make a great deal of sense > either. It was more of a catch-all class than anything. Absolutely:) Simon _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
