On Thu, 17 Jul 2003 13:44:46 +0300 (EEST) Nerijus Baliunas <[EMAIL PROTECTED]> wrote:
> On Thu, 17 Jul 2003 11:53:56 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL > PROTECTED]> wrote: > VZ> So maybe actually we do want to have something like this, after the move > VZ> in your example above: > VZ> > VZ> [A] > VZ> [A/B] > VZ> ... all data for the folder B ... > VZ> VisibleParent=C # folder tree checks this > VZ> > VZ> [C] > VZ> [C/B] > VZ> LinkTo=A/B # or "AliasFor" > VZ> > VZ> Of course, we can have more than one LinkTo but a whole chain of them... > Isn't it what Xavier and Robert discussed and decided against it? It looks like... Is there a problem in using the identifier as your '[A]' or '[A/B]'? > VZ> Another possibility I see is to simply forbid changing the parent, i.e. > VZ> renaming/moving folders should only be allowed between siblings. This is > VZ> more restrictive, of course > It would be unusable, at least for me. Moving between siblings means only > changing appearance order in the folder list, which I almost never use (if > we don't count renaming). What I use most is changing parents. <aol> Me too. </aol> -- Xavier Nodet "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." - Benjamin Franklin, 1759.
pgp00000.pgp
Description: PGP signature
