On Tue, Jul 19, 2011 at 21:27, Hyrum K Wright <hyrum_at_hyrumwright.org> wrote:
> Recently I've noticed several people alude to Editor v2 (Ev2) in both
> IRC and on this mailing list. While I know a header file and
> preliminary API has been scoped out, I'm curious as to what The Plan
> is. Are folks trying to get this into 1.8?
Unclear. It is very interesting work for me, so I would probably bring
in *some* level of Ev2 support. I cannot forsee a wholesale conversion
across the entire project.
For example, maybe provide support for an Ev2 editor from ra_serf, and
teach the commit system how to drive it. Or maybe there is an Ev2 ->
Ev1 shim so the commit driver only needs to know about Ev2. Haven't
really decided where the right vector is, in order to to partial
conversions. One option is an Ev2 layer in WC that higher levels (and
the update_editor) could drive. This might actually help in some of
the "move" stuff that stsp is working on.
> What's the general order for development?
Dunno. See above.
> What other work needs to be done to support this new
> API? Who are the principals developers interested in moving this
Lots of work. I believe it can be staged, rather than wholesale. Just
gotta find the cracks where that can happen. I've also considered
using it as a new FS API.
> And for the record, what are the benefits expected from all this work?
Atomicity, cleaner memory/pool handling, better debug support, much
more understandable, more clear and clean, etc. Read
notes/editor-v2.txt... that has some data that may help to understand
what/why. One simple effect: it gets rid of the cancellation editor,
the debug editor, another commit debug editor, and the default editor.
All gone. All built-in.
Received on 2011-07-20 05:44:11 CEST