[#5030] Improvements for namespace folder list
Summary Improvements for namespace folder list
Queue IMP
Queue Version HEAD
Type Enhancement
State Assigned
Priority 1. Low
Owners Horde Developers
Requester Jan Schneider <jan (at) horde (dot) org>
Created 02/24/2007 (443 days ago)
Due
Updated 10/25/2007 (200 days ago)
Assigned 05/31/2007 (347 days ago)
Resolved
Attachments folder_tree.png Download
Milestone IMP 4.2
Patch

History
10/25/2007 Jan Schneider Comment #10
Priority ⇒ 1. Low
Reply to this comment
> Jan, is this still an issue for you? It's the only showstopper
> currently listed for IMP 4.2.

An issue yes, but definitely not a show stopper.
10/25/2007 Chuck Hagenbuch Comment #9 Reply to this comment
Jan, is this still an issue for you? It's the only showstopper currently listed for IMP 4.2.
07/17/2007 Michael Slusarz Comment #8
Taken from Michael Slusarz
Assigned to Horde DevelopersHorde Developers
Reply to this comment
> The virtual folders are fine again, but the shared folders still
> appear under public folders, and the empty shared folders node is
> still displayed.

I tried debugging this for hours and my tree looks identical to Jan's and I still could never reproduce.  So somebody that can reproduce this will have to take a look at this.
05/31/2007 Jan Schneider Comment #7
State ⇒ Assigned
Reply to this comment
The virtual folders are fine again, but the shared folders still appear under public folders, and the empty shared folders node is still displayed.
05/31/2007 Michael Slusarz Comment #6
State ⇒ Feedback
Reply to this comment
05/28/2007 Jan Schneider Comment #5
State ⇒ Assigned
Reply to this comment
My virtual folders are not displayed under the shared folders node. If using the alternative namespaces like described in this ticket earlier the shared folders are displayed under the public folders node.
05/27/2007 Michael Slusarz Comment #4
Priority ⇒ 2. Medium
Assigned to Michael Slusarz
Reply to this comment
04/13/2007 Chuck Hagenbuch State ⇒ Accepted
 
03/01/2007 Jan Schneider Comment #3 Reply to this comment
I think that would be a good compromise, especially since I've never seen multiple namespaces on a real world server.
03/01/2007 Michael Slusarz Summary ⇒ Improvements for namespace folder list
 
03/01/2007 Michael Slusarz Comment #2 Reply to this comment
I can see this in cases where there is only one namespace in a given type - we could simply display all folders in the base directory ("Shared Folders"/"Public Folders") like we do when one of these namespaces is blank.  However, if there are multiple namespaces for a given type we must display the way we currently do or else we risk collisions (i.e. if both shared folders contain a 'foo' mailbox, there is no way to display both of these if we have a flat display.
02/24/2007 Jan Schneider Comment #1
New Attachment: folder_tree.png Download
Queue ⇒ IMP
State ⇒ Feedback
Summary ⇒ Improvements for namspaced folder list
Type ⇒ Enhancement
Priority ⇒ 1. Low
Reply to this comment
I suggest to tweak the new folder tree view that separates public and shared folders from personal folders. We should not display the namespace value that is used for the public and shared namespaces at all.
E.g. if I use the altnamepace setting with Cyrus, the tree currently looks like in the attached screen shot. This is obviously redundant. The namespaces the in this case look like:
(("" ".")) (("Other Users." ".")) (("Shared Folders." "."))
But even without altnamespace (("INBOX." ".")) (("user." ".")) (("" ".")) it would make sense to remove the 'user' level from the 'Shared Folders' subtree.