Added the final piece - allowing a user to create namespaces in base 
level of public/shared has the blank namespace.



Closing ticket.  Further issues should be opened in new tickets.

Works really great now.

This has been finished.

Should be fixed, hopefully correct.

Warning: Missing argument 1 for _getnamespace() in 
/home/jan/headhorde/imp/lib/IMAP/Tree.php on line 1860



But it works now, yay! I do think though, that we shouldn't sort the 
Shared Folders, Public Folders and Virtual Folders into the normal 
folders, but display them at the end of the tree instead.

http://lists.horde.org/archives/cvs/Week-of-Mon-20070212/065339.html

No, I don't have altnamespace enabled. My namespaces look like:

(("INBOX." ".")) (("user." ".")) (("" "."))

With altnamespace it would look like:

(("" ".")) (("Other Users." ".")) (("Shared Folders." "."))

Are your shared/public folders showing up under a separate folder 
entitled "Shared Folders" or "Public Folders"?  Those folders will be 
located alphabetically in your folder list.

No more error messages, but the sorting is still unchanged.

Where does this get us?

http://lists.horde.org/archives/cvs/Week-of-Mon-20070205/065278.html

http://lists.horde.org/archives/cvs/Week-of-Mon-20070205/065279.html

Nothing changes if I turn the pref on. After loggin in again, I get 
the following warning:

Warning: Invalid argument supplied for foreach() in 
/home/jan/headhorde/imp/lib/IMAP/Tree.php on line 1141

The sorting still doesn't change though.

Initial code committed to HEAD.

I haven't yet decided the final display details.  And I'm thinking 
this should be a preference.

Michael, what are your current thoughts on this?

Jan provides a good framework to start playing around with.  Bumping.

I agree with what Jan said.

I just compared Outlook, Thunderbird, KMail, and Mail.app. None of 
these is hiding the namespaces, so they don't have any problems with 
this. I still think it's a good idea that we *do* hide them.

I don't think it would get too cluttered if we mix hiding namespaces 
and grouping namespaces. The namespaces should be grouped at the end 
of the folder list under top level containers with some meaningful 
name (Shared Folders, Public Folders), like Virtual Folders is now 
already. I also think we should move the vfolder container to the 
bottom of the list too. They really aren't regular folders, so 
"hiding" them between the other folders doesn't get us anywhere and is 
confusing IMO.

I think this is starting to get too cluttered.  We either need to let 
users be able to manipulate all the namespaces (which we don't 
currently allow the user to do - see, e.g., hiding personal namespaces 
from user; not being able to add folders to a private namespace if it 
is the "blank" namespace) or hide all namespace information from the 
user (which is our current UI plan).  Adding "containers" for 
different namespaces starts to mix the two.

This is not a bug - rather, it is a UI issue.

What if we create a container for each namespace?



-- Personal --

Inbox.a

Inbox.z

-- Public --

m



Or does that create tou much clutter?

I personally find it confusing, but I know what namespace this folder 
is coming from. And the old behaviour was different, that confused me 
too.



I'm fine with it if the change was intended, but I'm still not sure if 
it is a good idea. Even if people shouldn't have to know about 
namespaces, it might be desirable for the user to distinguish 
private/personal folders from public/shared folders. Dunno.

I think you are incorrect - this is actually a feature that was quite 
annoying to code.  Take this example given your namespaces:

INBOX.a   (private)

INBOX.z    (private)

m          (public)



Since we strip private namespaces when displaying folders, our folder 
list will actually looks like this when outputting to the screen:

a

z

m



Showing folders like this is obviously *very* confusing - why is m 
sorted after z?  So we need to show folders like the following:

a   (INBOX.a)

m  (m)

z    (INBOX.z)



Which should be what we are doing now.  So you are correct that we are 
mixing personal and private namespaces, but that's perfectly fine and 
actually desired.

I'm sorry, but sorting is broken again. Folders from the public 
namespace are sorted into the personal folders.



NAMESPACE (("INBOX." ".")) (("user." ".")) (("" "."))