Summary: | [Qt] Review all new API in Qt 4.6 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Simon Hausmann <hausmann> | ||||||
Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | ariya.hidayat, ben, commit-queue, eric, kenneth, laszlo.gombos, tonikitoo, vestbo, yael | ||||||
Priority: | P2 | Keywords: | Qt | ||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Bug Depends on: | 30530, 30630, 30710, 30772, 30773, 31249 | ||||||||
Bug Blocks: | 29799 | ||||||||
Attachments: |
|
Description
Simon Hausmann
2009-09-29 03:53:00 PDT
We had a quick round of API review with Matthias here at the DevDays and came up with the following suggestions for changes: * QWebFrame::clipContentsToViewport: 1) Remove the property 2) Deprecate QWebFrame::render() 3) Introduce QWebFrame::paint(QWebFrame::PaintOptions opts = QWebFrame::AllElements), so that one can for eaxmple call frame->paint(QWebFrame::Contents); frame->paint(QWebFrame::Contents | QWebFrame::ScrollBars); * QWebFrame::scrollBarGeometry(): good name, keep it * QWebPage::fixedContentsSize property: 1) Rename to preferredContentsSize Created attachment 41320 [details]
Rename the fixedContentsSize property
Comment on attachment 41320 [details]
Rename the fixedContentsSize property
Thanks! Please fix the spelling of my first name in the ChangeLog when landing though ;-)
Comment on attachment 41320 [details] Rename the fixedContentsSize property Clearing flags on attachment: 41320 Committed r49766: <http://trac.webkit.org/changeset/49766> All reviewed patches have been landed. Closing bug. Closed by bot, but this is a tracker-bug Created attachment 41443 [details]
First part of the clipContentsToViewport fix (introduce paint method, deprecate render)
Follow up patch will remove the clipContentsToViewport property Please open a new bug for new fixes. If you want to use tracker bugs, you should open bugs for all the individual fixes and marked them blocked on this one. I think this bug should be closed and the patch moved to a new bug. I agree with Eric, we should have individual blocker-bugs for each patch. But do we really need to delete this bug? Can't we obsolete/remove the patches and just keep on using it to track the API reviews? Some comments after a small session we had in Oslo. The only API left now should be QGraphicsWebView. 1. QWebFrame::loadStarted() and QWebFrame::loadFinished() Do we need these? It's duplicating the problem of the 'ok' argument. 2. QWebKitVersion - Who's going to use this? Are we exposing a version that has no real use? 3. QWebPluginDatabase Propose to make this private. See bug 30775 4. QWebSecurityOrigin::add/remove/LocalScheme() Rename to register*? 5. QWebSecurityOrigin::whitelistAccesFromOrigin() ++ Rename to q_drt (they were added for DRT) 6. Misc QWebPage::shouldInterupJavaScript() - did we decide to remove this? QWebSettings::defaltTextEncoding() - QTextCodec? QWebView::guessUrlFromString()- Remove from WebKit, lives in QUrl now QWebSettings::setPrintingMinimumShrinkFactor etc 4.6 or 4.7? Tor I'd like to request discussion for https://bugs.webkit.org/show_bug.cgi?id=30771 if possible. I sent an email to webkit-qt ML ealier today titled "qweb{page,view} and qgraphicswebview createWindow method." (In reply to comment #11) > Some comments after a small session we had in Oslo. The only API left now > should be QGraphicsWebView. > > 1. QWebFrame::loadStarted() and QWebFrame::loadFinished() > > Do we need these? It's duplicating the problem of the 'ok' argument. I think Yael could answer that. > 2. QWebKitVersion - Who's going to use this? Are we exposing a version that has > no real use? Useful for changing the user agent, you want to set the right webkit version. Also useful for browsers. > Rename to q_drt (they were added for DRT) In that case I agree. > 6. Misc > > QWebPage::shouldInterupJavaScript() - did we decide to remove this? No we did not, but at least there should be a setting to set the timeout. > QWebView::guessUrlFromString()- Remove from WebKit, lives in QUrl now It does? since when? Thiago was opposed to that. 5. QWebSecurityOrigin::whitelistAccesFromOrigin() ++ Rename to q_drt (they were added for DRT) DONE. Landed in 50166.
> > QWebView::guessUrlFromString()- Remove from WebKit, lives in QUrl now
>
> It does? since when? Thiago was opposed to that.
OK, it was added, but due to license problems it will be removed from Qt by Thiago and readded by Benjamin (icefox). When this has been done I will remove the method. This should happen early tomorrow morning.
(In reply to comment #13) > (In reply to comment #11) > > Some comments after a small session we had in Oslo. The only API left now > > should be QGraphicsWebView. > > > > 1. QWebFrame::loadStarted() and QWebFrame::loadFinished() > > > > Do we need these? It's duplicating the problem of the 'ok' argument. > > I think Yael could answer that. > Looking at svn logs, I think Simon added these signals for DRT tests, These are not the signals that I have added. (In reply to comment #16) > (In reply to comment #13) > > (In reply to comment #11) > > > Some comments after a small session we had in Oslo. The only API left now > > > should be QGraphicsWebView. > > > > > > 1. QWebFrame::loadStarted() and QWebFrame::loadFinished() > > > > > > Do we need these? It's duplicating the problem of the 'ok' argument. > > > > I think Yael could answer that. > > > > Looking at svn logs, I think Simon added these signals for DRT tests, These are > not the signals that I have added. Rename to q_drt (they were added for DRT) then. Closing this bug as all the API has been reviewed and fixed. We're past the deadline of API changes for Qt 4.6 now. |