Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(44)

Issue 2247003005: Eliminate class TextCheckingHelper (Closed)

Created:
4 years, 4 months ago by Xiaocheng
Modified:
4 years, 4 months ago
Reviewers:
yosin_UTC9
CC:
blink-reviews, chromium-reviews, groby+blinkspell_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@CleanupUnifiedTextChecker
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Eliminate class TextCheckingHelper The class TextCheckingHelper was introduced for helping synchronous spell checking, which can now only be initiated from |advanceToNextMisspelling()|. Given its very limited use today and the simplicity of its logic, this patch eliminates the class and merges its code into the SpellChecker class to simplify the code base. BUG=633509 TEST=n/a; no behavior change

Patch Set 1 #

Total comments: 11
Unified diffs Side-by-side diffs Delta from patch set Stats (+125 lines, -565 lines) Patch
M third_party/WebKit/Source/core/core.gypi View 1 chunk +2 lines, -2 lines 0 comments Download
M third_party/WebKit/Source/core/editing/spellcheck/SpellChecker.h View 1 chunk +4 lines, -0 lines 0 comments Download
M third_party/WebKit/Source/core/editing/spellcheck/SpellChecker.cpp View 5 chunks +115 lines, -4 lines 10 comments Download
D third_party/WebKit/Source/core/editing/spellcheck/TextCheckingHelper.h View 1 chunk +0 lines, -101 lines 0 comments Download
D third_party/WebKit/Source/core/editing/spellcheck/TextCheckingHelper.cpp View 1 chunk +0 lines, -308 lines 0 comments Download
A + third_party/WebKit/Source/core/editing/spellcheck/TextCheckingParagraph.h View 2 chunks +3 lines, -24 lines 0 comments Download
A + third_party/WebKit/Source/core/editing/spellcheck/TextCheckingParagraph.cpp View 3 chunks +1 line, -126 lines 1 comment Download

Depends on Patchset:

Messages

Total messages: 12 (6 generated)
Xiaocheng
PTAL.
4 years, 4 months ago (2016-08-16 05:32:33 UTC) #7
yosin_UTC9
Since, |SpellChecker::findMisspellings()| seems to be a new function rather than moving. Let's move it into ...
4 years, 4 months ago (2016-08-16 06:04:06 UTC) #8
yosin_UTC9
4 years, 4 months ago (2016-08-16 06:04:11 UTC) #9
Xiaocheng
> Since, |SpellChecker::findMisspellings()| seems to be a new function rather than moving. > Let's move ...
4 years, 4 months ago (2016-08-16 06:21:36 UTC) #10
yosin_UTC9
On 2016/08/16 at 06:21:36, xiaochengh wrote: > > Since, |SpellChecker::findMisspellings()| seems to be a new ...
4 years, 4 months ago (2016-08-16 06:41:47 UTC) #11
Xiaocheng
4 years, 4 months ago (2016-08-16 06:58:15 UTC) #12
On 2016/08/16 at 06:41:47, yosin wrote:
> On 2016/08/16 at 06:21:36, xiaochengh wrote:
> > > Since, |SpellChecker::findMisspellings()| seems to be a new function
rather than moving.
> > > Let's move it into |SpellChecker| in-place. Then move to
"SpellChecker.cpp" for ease of reviewing.
> > 
> > Sorry I'm not following. Could you explain?
> 
> We should have two patches:
> 1. Change "TextCheckingHelper.cpp" to change |static void findMisspellings()|
to |SpellChecker::findMispellings()| and its call sites. Note: no re-factoring.
> 2. Move |SpellChecker::findMispellings()| to "SpellChecker.cpp"

I still don't understand. What's the benefit of having two patches, at the cost
of complicating stuff by introducing an intermediate state?

Can we talk offline?

Powered by Google App Engine
This is Rietveld 408576698