On Thu, 17 Jul 2003 13:44:46 +0300 (EEST) Nerijus Baliunas <[EMAIL PROTECTED]> wrote:
NB> On Thu, 17 Jul 2003 11:53:56 +0200 (Romance Daylight Time) Vadim Zeitlin <[EMAIL PROTECTED]> wrote: NB> NB> VZ> So maybe actually we do want to have something like this, after the move NB> VZ> in your example above: NB> VZ> NB> VZ> [A] NB> VZ> [A/B] NB> VZ> ... all data for the folder B ... NB> VZ> VisibleParent=C # folder tree checks this NB> VZ> NB> VZ> [C] NB> VZ> [C/B] NB> VZ> LinkTo=A/B # or "AliasFor" NB> VZ> NB> VZ> Of course, we can have more than one LinkTo but a whole chain of them... NB> NB> Isn't it what Xavier and Robert discussed and decided against it? I'm not sure if it's exactly the same thing. I think the above is simpler. NB> VZ> Another possibility I see is to simply forbid changing the parent, i.e. NB> VZ> renaming/moving folders should only be allowed between siblings. This is NB> VZ> more restrictive, of course NB> NB> It would be unusable Well, no, it surely wouldn't be worse than now... NB> What I use most is changing parents. I'd like to move folders freely too but at the very least we should have special case for moving them without changing parents anyhow because it can be done much simpler and so I propose to start by doing this. Regards, VZ ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Mahogany-Developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/mahogany-developers
