RESOLVED FIXED112278
[BlackBerry] Add Proximity Detector.
https://bugs.webkit.org/show_bug.cgi?id=112278
Summary [BlackBerry] Add Proximity Detector.
gmak
Reported 2013-03-13 12:47:09 PDT
It detects blocks near the given point and returns the top left corner of the selected rect.
Attachments
Patch with changelogs (8.39 KB, patch)
2013-03-13 12:53 PDT, gmak
no flags
Patch with changelogs - style fixed (8.40 KB, patch)
2013-03-13 13:01 PDT, gmak
rwlbuis: review-
Patch with changelogs (8.39 KB, patch)
2013-03-13 13:23 PDT, gmak
no flags
Patch with changelogs (8.37 KB, patch)
2013-03-13 14:06 PDT, gmak
no flags
Patch (3.77 KB, patch)
2013-03-14 05:29 PDT, Alberto Garcia
no flags
gmak
Comment 1 2013-03-13 12:53:42 PDT
Created attachment 192969 [details] Patch with changelogs
WebKit Review Bot
Comment 2 2013-03-13 12:56:07 PDT
Attachment 192969 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebKit/ChangeLog', u'Source/WebKit/PlatformBlackBerry.cmake', u'Source/WebKit/blackberry/ChangeLog', u'Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp', u'Source/WebKit/blackberry/WebKitSupport/ProximityDetector.h']" exit_code: 1 Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:103: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:104: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:105: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:107: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:108: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:109: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:110: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:111: Weird number of spaces at line-start. Are you using a 4-space indent? [whitespace/indent] [3] Total errors found: 8 in 5 files If any of these errors are false positives, please file a bug against check-webkit-style.
gmak
Comment 3 2013-03-13 13:01:44 PDT
Created attachment 192975 [details] Patch with changelogs - style fixed
WebKit Review Bot
Comment 4 2013-03-13 13:09:45 PDT
Attachment 192975 [details] did not pass style-queue: Failed to run "['Tools/Scripts/check-webkit-style', '--diff-files', u'Source/WebKit/ChangeLog', u'Source/WebKit/PlatformBlackBerry.cmake', u'Source/WebKit/blackberry/ChangeLog', u'Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp', u'Source/WebKit/blackberry/WebKitSupport/ProximityDetector.h']" exit_code: 1 Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:108: When wrapping a line, only indent 4 spaces. [whitespace/indent] [3] Total errors found: 1 in 5 files If any of these errors are false positives, please file a bug against check-webkit-style.
Rob Buis
Comment 5 2013-03-13 13:11:59 PDT
Comment on attachment 192975 [details] Patch with changelogs - style fixed View in context: https://bugs.webkit.org/attachment.cgi?id=192975&action=review Can be cleaned up a bit more. > Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:18 > +using WTF::RefPtr; Should not be needed at all. > Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:19 > +using WTF::String; You may get away with discarding this one but it depends if it clashes with B::P::String.
gmak
Comment 6 2013-03-13 13:23:02 PDT
Created attachment 192983 [details] Patch with changelogs
Rob Buis
Comment 7 2013-03-13 13:34:59 PDT
Comment on attachment 192983 [details] Patch with changelogs View in context: https://bugs.webkit.org/attachment.cgi?id=192983&action=review > Source/WebKit/blackberry/WebKitSupport/ProximityDetector.cpp:104 > + bool equalPriorityAndCloser = priority == bestPriority && sqrt((double)contentPos.distanceSquaredToPoint(bestPoint)) > sqrt((double)contentPos.distanceSquaredToPoint(curRect.location())) I think parentheses would make this more readable, plus you can discard both sqrt in this case.
gmak
Comment 8 2013-03-13 14:06:28 PDT
Created attachment 192991 [details] Patch with changelogs
Rob Buis
Comment 9 2013-03-13 14:11:03 PDT
Comment on attachment 192991 [details] Patch with changelogs LGTM.
WebKit Review Bot
Comment 10 2013-03-13 14:51:47 PDT
Comment on attachment 192991 [details] Patch with changelogs Clearing flags on attachment: 192991 Committed r145757: <http://trac.webkit.org/changeset/145757>
WebKit Review Bot
Comment 11 2013-03-13 14:51:52 PDT
All reviewed patches have been landed. Closing bug.
Alberto Garcia
Comment 12 2013-03-14 05:29:18 PDT
Created attachment 193107 [details] Patch This will not compile, variable names are wrong. Here's the fix.
Rob Buis
Comment 13 2013-03-14 07:32:30 PDT
Comment on attachment 193107 [details] Patch Again, well spotted.
Alberto Garcia
Comment 14 2013-03-18 10:49:56 PDT
I think the patch was not commited, either we reopen this or I file a new bug.
Rob Buis
Comment 15 2013-03-18 11:09:19 PDT
Reopening to try to commit a fixup patch.
Rob Buis
Comment 16 2013-03-18 11:10:25 PDT
Comment on attachment 193107 [details] Patch Retrying.
WebKit Review Bot
Comment 17 2013-03-18 11:32:03 PDT
Comment on attachment 193107 [details] Patch Clearing flags on attachment: 193107 Committed r146090: <http://trac.webkit.org/changeset/146090>
WebKit Review Bot
Comment 18 2013-03-18 11:32:08 PDT
All reviewed patches have been landed. Closing bug.
gmak
Comment 19 2013-03-18 12:14:30 PDT
Thanks for catching that, I never compiled it because we have an older non-webkit compliant version internally.
Note You need to log in before you can comment on or make changes to this bug.