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

List:       kopete-devel
Subject:    [Kopete-devel] [Bug 73830] Be able to add sub groups to groups
From:       Jason Keirstead <jason () keirstead ! org>
Date:       2004-01-31 15:09:37
Message-ID: 20040131150937.20070.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=73830      




------- Additional Comments From jason@keirstead.org  2004-01-31 16:09 -------
Subject: Re: [Kopete-devel]  Be able to add sub groups to groups

On January 30, 2004 07:05 pm, Martijn Klingens wrote:
> ------- You are receiving this mail because: -------
> What if I move user Foo to group A/B/C here and then reconnect at work?
> 
> How is the nested group stored?

Like i said... *flattened*

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

What? What are you talking about here?

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

You flatten in libkopete.
 
> How do you associate the flattened group with Kopete's local group?

You don't have to, why would you? Server-side groups have unique IDs
that are stored as address book field sin the contact list. That is how MSN etc.
associate their groups with the Kopete groups. Since these protocols don't
have nested groups it's a non issue.

> 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?

I really don't understand this one. You cant have the same group in more than
one group, that's preposterous.
_______________________________________________
Kopete-devel mailing list
Kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]