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

List:       kopete-devel
Subject:    Re: [kopete-devel] Re: kdenetwork/kopete/kopete
From:       Matt Rogers <mattr () kde ! org>
Date:       2005-05-04 11:59:00
Message-ID: 200505040659.04320.mattr () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 04 May 2005 12:10 am, Olivier Goffart wrote:
> Le Mercredi 4 Mai 2005 05:24, Matt Rogers a écrit :
> > On Wednesday 20 April 2005 05:29 am, Olivier Goffart wrote:
> > > CVS commit by ogoffart:
> > >
> > > Add "set busy globally"  and "set invisible globally"  in the
> > > connection menu. This is a bit dirty, but i hope this is going to
> > > replaced by dynamic categories
> >
> > What's the difference between 'Busy' and 'Away'? Why are both needed?
>
> Most protocols have several status, including a Busy status.
>

'Busy' is the same as away in my book, and enough protocols don't have busy to 
justify it IMHO. It's just extra code that we don't need.

> > 'Invisible' makes more sense than 'Busy' does.
> >
> > And what's the deal with dynamic categories?
>
> cf Bug 57297  ( More granular global away settings )
>
> The goal is to be able to configure status categories.
> with an away message, and status for most protocols.
>
> Anyway, having a default set of good categories is already a good start.

I don't see why we need dynamic categories for that. This borders on too much 
configurability or overengineering from my POV.

Matt

[Attachment #5 (application/pgp-signature)]

_______________________________________________
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]