WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
47086
Remove unused code from gtk2drawing.c
https://bugs.webkit.org/show_bug.cgi?id=47086
Summary
Remove unused code from gtk2drawing.c
Carlos Garcia Campos
Reported
2010-10-04 07:42:26 PDT
Created
attachment 69633
[details]
Remove unused code That file was copied from mozilla and contains a lot of code that is not used by WebKit. Most of that unused code is uncompatible with gtk3, so removing it will make easier porting to gtk3.
Attachments
Remove unused code
(82.81 KB, patch)
2010-10-04 07:42 PDT
,
Carlos Garcia Campos
no flags
Details
Formatted Diff
Diff
Updated patch to remove unused code
(83.71 KB, patch)
2010-10-06 00:27 PDT
,
Carlos Garcia Campos
no flags
Details
Formatted Diff
Diff
New version of the patch
(83.65 KB, patch)
2010-10-06 09:15 PDT
,
Carlos Garcia Campos
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Martin Robinson
Comment 1
2010-10-04 12:40:14 PDT
We plan to fork this code when the styling changes for GTK+ land (to make it WebKit-y). Depending on the timetable for the styling updates, it may make sense to just use #ifdefs instead of trying to keep this code up to date.
Xan Lopez
Comment 2
2010-10-05 03:15:34 PDT
(In reply to
comment #1
)
> We plan to fork this code when the styling changes for GTK+ land (to make it WebKit-y). Depending on the timetable for the styling updates, it may make sense to just use #ifdefs instead of trying to keep this code up to date.
I suggested Carlos to fork it now, since keeping a single file that copes with both GTK+ 2 and the new drawing APIs already in GTK+ master would be an #ifdef nightmare.
Martin Robinson
Comment 3
2010-10-05 08:09:31 PDT
We should probably just bite the bullet and start transitioning away from the Mozilla theme drawing code. The files already diverge from the original code and we can use C++ features to hide the differences between GTK+ 2 and GTK+ 3.
Martin Robinson
Comment 4
2010-10-05 13:08:25 PDT
After discussing this with Xan via IRC, we decided that the right approach here was to start replacing the Mozilla code with our own rendering code in WebKit sooner, rather than later. I feel pretty confidant that we can maintain this. We'll also be able to start dealing with the GTK2/GTK3 compatibility issues using C++ sugar. In the interest of keeping things building with GTK3, I think we can start by removing the unused code. This patch needs a ChangeLog though.
Carlos Garcia Campos
Comment 5
2010-10-06 00:26:34 PDT
Yes, the idea was doing a plain port to gtk3 now, so that ephy/webkit can release for GNOME 2.91.0, further improvements or redesigns can be done on top of this.
Carlos Garcia Campos
Comment 6
2010-10-06 00:27:46 PDT
Created
attachment 69896
[details]
Updated patch to remove unused code Updated patch including the ChangeLog entry
Carlos Garcia Campos
Comment 7
2010-10-06 09:15:28 PDT
Created
attachment 69948
[details]
New version of the patch New version of the patch with the ChangeLog correctly formatted
Martin Robinson
Comment 8
2010-10-06 09:17:00 PDT
Comment on
attachment 69948
[details]
New version of the patch Looks good!
WebKit Commit Bot
Comment 9
2010-10-06 10:04:49 PDT
Comment on
attachment 69948
[details]
New version of the patch Clearing flags on attachment: 69948 Committed
r69205
: <
http://trac.webkit.org/changeset/69205
>
WebKit Commit Bot
Comment 10
2010-10-06 10:04:54 PDT
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug