Branko Čibej wrote:
On 14 Aug 2013 16:23, "Julian Foad" wrote:
>> > and also makes validating the drive easier.
>>
>> I'm not sure what you're thinking about validating the editor drive being
>> easier.
>
> Move away without a matching moved here (or the converse) is clearly invalid.
> It must b
On 14 Aug 2013 16:23, "Julian Foad" wrote:
>
> Branko Čibej wrote:
>
> > and also makes validating the drive easier.
>
> I'm not sure what you're thinking about validating the editor drive being
easier.
> - Julian
Move away without a matching moved here (or the converse) is clearly
invalid. It mu
Julian Foad writes:
>> As you pointed out when a copy replaces a mv-away it is still necessary
>> to alter-dir two different nodes at the same path:
>>
>> 1. alter-dir A (children={...})
>> 2. mv-away A (id=...)
>> 3. copy A (src=...)
>> 4. alter-dir A (children={...})
>
> Well,
Philip Martin wrote:
> Julian Foad writes:
>> Example 3: Swapping two directory levels
>>
>> | |
>> +--A --\ /--> +--A
>> | X |
>> +--B --/ \--> +--B
>>
>> 1. alter-dir A (children={}) ### Needed?
>>
>> 2. mv-away A
Branko Čibej wrote:
> Move away/from with Id is essentially introducing a namespace for temporary
> paths unrelated to the tree structure. Therefore you can change notation and
> keep only one move operation with three variants:
>
> move(a,b): direct move of node to new path
> move(a,tmp(1)): m
Philip Martin wrote:
[...]
>>> === Examples Solved ===
>>>
>>> Example 1:
>>>
>>> | |
>>> +--A mv--\ add--> +--A
>>> \ |
>>> \--> +--B
>>>
>>> 1. alter-dir / (children={A})
>
> Do we need to call alter-dir when
Julian Foad writes:
> Example 3: Swapping two directory levels
>
> | |
> +--A --\ /-->+--A
> | X |
> +--B --/ \--> +--B
>
> 1. alter-dir A (children={}) ### Needed?
>
> 2. mv-away A/B (id=”original A/B”)
>
> 3. alter-dir /
On phone so a bit constrained ...
Move away/from with Id is essentially introducing a namespace for temporary
paths unrelated to the tree structure. Therefore you can change notation
and keep only one move operation with three variants:
move(a,b): direct move of node to new path
move(a,tmp(1)): mo
Greg Stein writes:
> In the wiki page you started, I thought we already solved the move issue by
> using the original state for the source. (and remove rotate)
>
> I didn't read this treatise, cuz I think it has an incorrect starting
> assumption. You state early about sequential edits, when we r
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 ("fi
In the wiki page you started, I thought we already solved the move issue by
using the original state for the source. (and remove rotate)
I didn't read this treatise, cuz I think it has an incorrect starting
assumption. You state early about sequential edits, when we relaxed that a
bit due to needi
11 matches
Mail list logo
