On Wed, Jul 20, 2011 at 12:40:06PM +0200, Bert Huijben wrote:
> It might be useful to use editor v2 for sending over file moves, but this is
> not a requirement for handling file moves.
> We overloaded the entry props feature a few times before and there is no
> reason why we can't get file moves working properly on just the old editor.
I was under the impression that the old editor interface was
the limiting factor here, in particular the (lack of) parameters
we pass to certain functions.
Would we not need to rev the editor vtable for this?
Of course, revving that interface is a lot simpler than implementing
editorv2, but I thought we'd take the time to do things "right" instead
of adding hacks upon hacks to get things working with the old interface.
But I am definitely not complaining if we can get moves working without
editorv2 because that means we'll get user-visible results much quicker.
> We don't need a new editor for improving automatic tree conflict handling.
> Tree conflicts and editor limitations are different problems which can be
> solved independently as well.
> The project of adding editorv2 is large enough by itself without tying all
> other issues to it.
Sounds good to me. I don't know exactly how you would solve it,
but I'll get back to you about this when I am ready to send moves :)
Received on 2011-07-20 12:54:39 CEST