Re: Algorithms for Editing Operations

I absolutely agree too. I had a pleasure to implement some of the
algorithms you're referring to or maintain a code implementing them so I
can imagine the scale of the problem. I'm sure that designing algorithms
and creating tests for them which would include more complex scenarios is,
besides a huge amount of work, a road to nowhere, because there are so many
possible behaviours that there will always be a significant group of people
dissatisfied with the results.

Furthermore, there's no popular standard which we could follow while
designing these algorithms. The popular editors like MSWord or Google Docs
are not HTML editors and the content they create is not meant to be a
semantic HTML, so many solutions cannot be adopted by us and sticking too
closely to them would lead to inconsistency or overcomplicating things and
creating a bad markup. Therefore, in my opinion, our goal should to produce
as simple and as semantic markup as possible.

On Fri, Nov 7, 2014 at 2:20 AM, <chaals@yandex-team.ru> wrote:

> Abserlutely!!!
>
> Seriously, I think we should ask the browser to handle the things that
> really are clear, but wherever we find ambiguity we punt to the app.
>
> Which is exactly what I think you propose.
>
> cheers
>
> 07.11.2014, 01:09, "Ben Peters" <Ben.Peters@microsoft.com>:
> > I have begun to research algorithms for editing, including insert text,
> insert content, delete content, insert newline, and replace content. I
> believe our goal should be to have consistent behavior that is reasonable
> and simple. In order to make it lightweight and easy to agree on, I think
> it should have very few heuristics and should instead rely on well-defined
> simplicity. This will result in imperfect, but consistent behavior.
> Frameworks and sites can implement their own complex heuristics or custom
> behavior using Intention Events. Thoughts?
> >
> > Ben
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
>
>


-- 
Piotrek Koszuliński
CKEditor JavaScript Lead Developer