[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 73830] Be able to add sub groups to groups
From:       Martijn Klingens <klingens () kde ! org>
Date:       2004-01-30 23:05:12
Message-ID: 20040130230512.5230.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=73830      




------- Additional Comments From klingens@kde.org  2004-01-31 00:05 -------
Subject: Re: [Kopete-devel]  Be able to add sub groups to groups

On Friday 30 January 2004 23:04, Jason Keirstead wrote:
> Not quite accurate. I feel you suffer from MSN syndrome... just because
> something is not possible in MSN does not mean it should be abandoned
> everywhere.

I don't think the distinction between requiring a server side list or just 
merely supporting it matters at all. It explains your wording in the previous 
comment, but that still doesn't change the fact that 6 out of 9 protocols 
have support for server side lists, of which only one supports nested groups.

That means that we need ugly flattening code in 5 out of 9 plugins to sync 
properly to and from the server.

What if I move user Foo to group A/B/C here and then reconnect at work?

How is the nested group stored?

How does Kopete know if I mean a nested group or a literal '/' character (or 
whatever other delimiter)?

How can we avoid a ton of code duplication in the syncing and flattening?

How do you associate the flattened group with Kopete's local group?

How do you allow to have both a literal group "A/B/C" _AND_ a group A at the 
same time? Or worse, a group "B" inside "A" at the same time?

Just some random questions to point out that this is not "trivial" and that  
"just flatten the groups when they export them to the server" is not easy to 
get right at all.
[prev in list] [next in list] [prev in thread] [next in thread]