plugin:find and replace move to trunk

[Garry Yao]

Find and replace plugin is required to move to trunk.

[Garry Yao]

Remove some unnecessary lines of change

[Garry Yao]

This patch make the following changes to Martin's initial codes:

1. Simplify the CharacterWalker by avoid using events internally, same reason as #2876.
2. Make the pattern matchable on inline elements edge, e.g. <span>
3. Introduce replace and replaceAll feature.
4. Make search start right from pre-selected position.
5. Add WholeWord match pattern validation based on find text pattern.
6. Make find and search tabs share same values on common fields when switching between them.
7. Fix a minor bug in _source/core/dom/document.js about createText

Martin, please give comments on it.

[Garry Yao]

Cleanning up codes.

[Frederico Caldeira Knabben]

This patch is proposing changes to "_source/plugins/find/dialogs/find.js", which is not available. I think this is not a patch for trunk.

[Garry Yao]

Yes,I've aligned the patch with trunk, please go ahead with the reviewing.

[Martin Kou]

Still a number of problems:

1. The dialog crashes in IE at opening.
2. editor.lang.findAndReplace.replaceSuccMsg is missing in the language file.
3. The dialog currently uses selectRanges() to highlight find results. This is not acceptable because it does not work in IE - sure the selection would still be visible in IE, but IE only allows one selection in each browser window so as soon as the user clicks on the dialog the highlight would be lost. I understand that such highlight logic would depend on #2768, which is not committed yet. But #2768's proposed patch is already working to some degree and it should be possible to propose a patch for the find dialog in conjunction with #2768's changes.
4. The editor window does not scroll to the find results.

Since this feature is urgently needed, and I don't see you on Skype today, I'm taking over this ticket.

[Martin Kou]

The replace function in the new patch crashes in IE, but after some investigations it's found to be a bug in the CKEDITOR.dom.range::extractContents() function.

Other features should be fully working.

[Martin Kou]

The patch includes the changes in #2768 for making the find results highlight work. To remove those changes, simply remove all the changes in _source/plugins/styles/plugin.js.

[Frederico Caldeira Knabben]

• The following case is not working:

1. Open the replace dialog.
2. Type "a" into the find field.
3. Type "AAA" into the replace field.
4. Click "Replace" several times.

Note that when clicking replace, the editor correctly selects the next "a" occurrence, but it incorrectly starts this search at the previous selection position, instead of after the replacement text. It results in a endless replacement inside the replaced text.

• Please change the alert message from "Successfully replaced %1 finds." to "%1 occurrence(s) replaced".

• Is it possible to disable the "Match whole word" checkbox, instead of removing it when typing non words? Actually, I would leave it always available, because it makes sense to match "Chapter 3" and not "Chapter 30".

• deleteContents should be used instead of extractContents. But it's still broken in IE. It's quite a serious break (content lost) so a fix for it must be included into the patch.

[Martin Kou]

Fixed with [3902].