My intention is to present possible designs for Ev2, and allow us to consider
which we prefer. In particular, we need to decide how important it is to
adhere to each of the principles including:
- the Once Rule
- avoidance of temporary paths (closely related to Once Rule)
- alter-dir ("final set of children = {...}") before altering dir's children
- sequential modification
since different designs may trade off one of these against the others.
Greg Stein wrote:
> In the wiki page you started, I thought we already solved the move
> issue by using the original state for the source. [...]
No, we didn't come up with an actual solution, we came up with an idea that
*might* lead to a solution -- it felt like it should. My gut feeling is it
doesn't play well with the Ev2 principles, but I am still going to explore that
idea further as a possible alternative and present either how it could work or
why it couldn't.
- Julian
> On Aug 12, 2013 10:43 AM, "Julian Foad" <julianf...@btopenworld.com> wrote:
>> TLDR: Ev2 move support doesn't work with the "move" and "rotate"
>> instructions as currently defined, and I propose that it could work
>> instead with separate "move-away" and "move-here" instructions.
[...]
