RESOLVED FIXED96769
[GTK] Don't use the C API internally in WebKitBackForwardList
https://bugs.webkit.org/show_bug.cgi?id=96769
Summary [GTK] Don't use the C API internally in WebKitBackForwardList
Carlos Garcia Campos
Reported 2012-09-14 06:42:27 PDT
Use the C++ classes instead.
Attachments
Patch (19.10 KB, patch)
2012-09-14 06:46 PDT, Carlos Garcia Campos
no flags
Updated patch to apply on current git master (19.10 KB, patch)
2012-10-01 08:42 PDT, Carlos Garcia Campos
gustavo: review+
Carlos Garcia Campos
Comment 1 2012-09-14 06:46:49 PDT
Carlos Garcia Campos
Comment 2 2012-10-01 08:42:39 PDT
Created attachment 166481 [details] Updated patch to apply on current git master New patch in trunk broke this one
WebKit Review Bot
Comment 3 2012-10-01 08:46:35 PDT
Thanks for the patch. If this patch contains new public API please make sure it follows the guidelines for new WebKit2 GTK+ API. See http://trac.webkit.org/wiki/WebKitGTK/AddingNewWebKit2API
Mario Sanchez Prada
Comment 4 2012-10-03 01:31:27 PDT
Comment on attachment 166481 [details] Updated patch to apply on current git master View in context: https://bugs.webkit.org/attachment.cgi?id=166481&action=review This patch is pretty straightforward and I have not much to comment here. LGTM > Source/WebKit2/UIProcess/API/gtk/WebKitBackForwardList.cpp:58 > + WebBackForwardList* webList; I would probably name it backForwardList instead of webList. But I'm not genius choosing names either, so take it as a subjective opinion. > Source/WebKit2/UIProcess/API/gtk/WebKitBackForwardList.cpp:140 > +WebKitBackForwardList* webkitBackForwardListCreate(WebBackForwardList* webList) Ditto > Source/WebKit2/UIProcess/API/gtk/WebKitBackForwardListItem.cpp:32 > + RefPtr<WebBackForwardListItem> webListItem; And here too. Or maybe just listItem here, not to make it too long
Carlos Garcia Campos
Comment 5 2012-10-03 01:35:44 PDT
(In reply to comment #4) > (From update of attachment 166481 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=166481&action=review > > This patch is pretty straightforward and I have not much to comment here. LGTM > > > Source/WebKit2/UIProcess/API/gtk/WebKitBackForwardList.cpp:58 > > + WebBackForwardList* webList; > > I would probably name it backForwardList instead of webList. But I'm not genius choosing names either, so take it as a subjective opinion. This was wkList before, I think, I renamed to webList to avoid confusion with C API variables.
Gustavo Noronha (kov)
Comment 6 2012-10-17 05:33:21 PDT
Comment on attachment 166481 [details] Updated patch to apply on current git master View in context: https://bugs.webkit.org/attachment.cgi?id=166481&action=review >>> Source/WebKit2/UIProcess/API/gtk/WebKitBackForwardList.cpp:58 >>> + WebBackForwardList* webList; >> >> I would probably name it backForwardList instead of webList. But I'm not genius choosing names either, so take it as a subjective opinion. > > This was wkList before, I think, I renamed to webList to avoid confusion with C API variables. How about naming it items or backForwardItems? backForwardList is a bad name I think because it's the name of the object that holds this private structure in most cases. This is the list of backForwardItems.
Carlos Garcia Campos
Comment 7 2012-10-17 08:46:25 PDT
(In reply to comment #6) > (From update of attachment 166481 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=166481&action=review > > >>> Source/WebKit2/UIProcess/API/gtk/WebKitBackForwardList.cpp:58 > >>> + WebBackForwardList* webList; > >> > >> I would probably name it backForwardList instead of webList. But I'm not genius choosing names either, so take it as a subjective opinion. > > > > This was wkList before, I think, I renamed to webList to avoid confusion with C API variables. > > How about naming it items or backForwardItems? backForwardList is a bad name I think because it's the name of the object that holds this private structure in most cases. This is the list of backForwardItems. Sure!
Carlos Garcia Campos
Comment 8 2012-10-17 08:48:00 PDT
Note You need to log in before you can comment on or make changes to this bug.