Bug 112261 – [WK2][EFL] Mark not implemented methods in TextCheckerEfl

• Status: RESOLVED
• Resolution: FIXED
• Component: WebKit EFL

[Grzegorz Czajkowski]

As a continuation of bug 111713 I'd like to prose further improvements of EFL's TextChecker.

It's no need to call client's methods in TextCheckerEfl if they are not implemented.
At the moment, they are using internal WK2 WebTextChecker class wich is not recommended.
It's better to mark them as not implemented unless we provide proper implementation.

[Grzegorz Czajkowski]

Created attachment 192924 [details]
proposed patch

[Mikhail Pozdnyakov]

Comment on attachment 192924 [details]
proposed patch

Makes sense.

[Mikhail Pozdnyakov]

(In reply to comment #2)
> (From update of attachment 192924 [details])
> Makes sense.
The class TextChecker is WK2 generic so we cannot just remove those methods, right?

[Grzegorz Czajkowski]

(In reply to comment #3)
> (In reply to comment #2)
> > (From update of attachment 192924 [details] [details])
> > Makes sense.
> The class TextChecker is WK2 generic so we cannot just remove those methods, right?

Exactly, thanks for the review!

[Gyuyoung Kim]

Comment on attachment 192924 [details]
proposed patch

View in context: https://bugs.webkit.org/attachment.cgi?id=192924&action=review

Should we remove this at the moment ? Is it better to remove when we prepare a patch for new implementation ?

> Source/WebKit2/ChangeLog:10
> +        class wich is not recommended.

Typo: wich ?

[Grzegorz Czajkowski]

(In reply to comment #5)
> (From update of attachment 192924 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=192924&action=review
> 
> Should we remove this at the moment ? Is it better to remove when we prepare a patch for new implementation ?

IMO, it's better to remove it. Grammar checking implementation is more complicated than the spell checking due to libraries/services unavailability. We are not sure whether the implementation will be provided.

Secondly our text checker doesn't implement them (the client's callbacks are not initialized) so it doesn't make sense to invoke them.

Finally, Kenneth mentioned that we shouldn't call the client's methods in TextCheckerEfl as the matter of fact we use an internal WebKit implementation (with Enchant support). It'd be better to call them directly as Mac is doing in their TextCheckerMac.mm

> 
> > Source/WebKit2/ChangeLog:10
> > +        class wich is not recommended.
> 
> Typo: wich ?

Thanks. If you don't mind I fix it before landing.

[Gyuyoung Kim]

Ok, looks make sense.

[Grzegorz Czajkowski]

Committed r147993: <http://trac.webkit.org/changeset/147993>