--===============0420701561==
Content-Type: multipart/signed;
  boundary="nextPart1967171.xpLjcHCfuo";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1967171.xpLjcHCfuo
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 06 May 2005 10:58 am, Ga=EBl Beaudoin wrote:
> Having a consistent and clean interface is great, but I agree with Olivier
> Goffart : msn and icq for example have far more status and they're far fr=
om
> useless. "Out to lunch" isn't the same as "away" or "occupied".
>

i would argue that it is the same, to a certain extent, and would rather ca=
ll=20
it a specialization of the "away" status.


> Would it be possible to have global/default settings with for example the
> status that exists in every protocols and, also, the ability to set up
> custom status for which we could choose which status to use in each
> protocol.
>

god no, not another option. at least not until we can sort out the current=
=20
ones we have.

> Kopete need this feature. Personally it doesn't bother me so much but
> people coming from other IM programs simply don't understand why it is not
> possible.
>
> Ga=EBl Beaudoin

Sorry, I'm still not convinced it's all that necessary to add every single=
=20
unique status. I say if two or three protocols can support a status, we can=
=20
add it, but otherwise, i see no point, it's just clutter in the menu.

Matt

>
> Le Vendredi 6 Mai 2005 02:30, Matt Rogers a =E9crit=A0:
> > On Thursday 05 May 2005 07:21 am, Olivier Goffart wrote:
> > > Le Jeudi 5 Mai 2005 13:40, Matt Rogers a =E9crit=A0:
> > > > On Thursday 05 May 2005 02:39 am, Olivier Goffart wrote:
> > > > > Have you noticed that MSN has more than 2 online status.  There is
> > > > > busy, be right back, on the phone.
> > > > > ICQ has also occupied, do not distrub, free for chat.  Same for
> > > > > Jabber, Yahoo, GG, ....
> > > > >
> > > > > If i want to set the status to busy globally, i have to select
> > > > > select my status in each different account.
> > > > > I don't see why one could go Away, and not Busy, Invisible, Free
> > > > > for Chat, Be right back globally.
> > > >
> > > > Because those statuses don't exist in other protocols! Kopete is a
> > > > multi-protocol client, or have you forgotten that? Global options
> > > > that cover only a few protocols don't make sense, IMNSHO.
> > >
> > > I don't want Kopete be the lower denominator.
> > > If the a status doesn't exist in a category for a protocol, then Kope=
te
> > > will try to fall back to the status which fit the more in the categor=
y.
> >
> > From my POV, it's not about following the lowest common denominator. It=
's
> > about being able to provide a consistent and usable interface, and addi=
ng
> > entries to the global menu that change just a few (or even one) protocol
> > to the correct status surely won't be usable, since you're looking at an
> > entry for every unique status in a protocol.
> >
> > > see this mail
> > > http://lists.kde.org/?l=3Dkopete-devel&m=3D111316716601158&w=3D2 you =
probably
> > > haven't read ( you probably was out the mailing list at this time).
> >
> > and it's so long, that i have no interest in reading it.
> >
> > Matt
>
> _______________________________________________
> kopete-devel mailing list
> kopete-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kopete-devel

--nextPart1967171.xpLjcHCfuo
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCfWItA6Vv5rghv0cRApHfAJ9QiQkmDkAd6O/ZPzGUs1PO1K+NqgCfdrNa
10lIp+scSeunnKmANLEoDA8=
=rvvI
-----END PGP SIGNATURE-----

--nextPart1967171.xpLjcHCfuo--

--===============0420701561==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel

--===============0420701561==--