On Thu, 17 Jul 2003 11:40:14 +0200 (CEST) Robert Vazan <[EMAIL PROTECTED]> wrote:

RV> If I move folder A/B to folder C, it will have identifier A/B and
RV> visible name C/B. However when folder tree tries to enumerate subfolders
RV> of C, it will not find B,

 Oh yes, I see. This is a really bad problem however.

RV> because it is located under its id A/B. For
RV> this reason, folder tree must prescan all folders for visible names and
RV> construct its own private tree of visible names.

 It's not a solution because we're back at case #1: what happens now when a
folder is renamed? The tree needs to be notified and rebuild all its
internal data structures... Well, ok, it's doable, but not ideal.

 Worse, I was only thinking about name (!= path) changes before and so
didn't realize that the 1 to 1 mapping between config groups and folder
tree would be broken with this change. Now that I do, I like it much, much
less.

 So maybe actually we do want to have something like this, after the move
in your example above:

        [A]
        [A/B]
        ... all data for the folder B ...
        VisibleParent=C # folder tree checks this

        [C]
        [C/B]
        LinkTo=A/B         # or "AliasFor"

Of course, we can have more than one LinkTo but a whole chain of them...


 Another possibility I see is to simply forbid changing the parent, i.e.
renaming/moving folders should only be allowed between siblings. This is
more restrictive, of course, but this is by far the most common case and
much simpler to implement. So when I (or anyone else) starts working on it
I think it would be best to first implement renaming between siblings only
properly and only then think about anything else.

 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

Reply via email to