From quanta-devel  Tue Aug 23 03:34:47 2005
From: Jens Herden <jens () kdewebdev ! org>
Date: Tue, 23 Aug 2005 03:34:47 +0000
To: quanta-devel
Subject: Re: [quanta-devel] team configuration is broken
Message-Id: <200508231034.52317.jens () kdewebdev ! org>
X-MARC-Message: https://marc.info/?l=quanta-devel&m=112476814313251
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1127420436=="

--===============1127420436==
Content-Type: multipart/signed;
  boundary="nextPart1939657.cKe4FIjElK";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1939657.cKe4FIjElK
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

> > working on it, tell me that I should ask Erik
>
> ...the Viking. ;-)

Sorry Eric! My German brain did not work correctly ;-)

> > Using two different ways for similar tasks (sending email and sending
> > annotations) is quite a bad design, because it is hard for the user
> > to follow this concepts. You force the user to mix two concepts of
> > addressing people here.
>
> Sending email is related to actions, while writing addressed annotations
> are related to the workflow (commenting the code). I don't see where do
> they intersect.

You are in the typical developer trap here. A user is not knowing what you=
=20
think a feature is meant for. In fact users will use your feature for=20
whatever they think it is good for. If someone wants to ask her co-develope=
r=20
to become his wife via annotations why not?=20
So if you think about something try to break it down to the base of what it=
=20
does. It is not workflow or commenting it is simply sending some informatio=
n=20
to a person. This person needs to be identified.
Sending mails via event actions is the same principle. Sending information =
to=20
a person and you need an address.=20
Both is about how to identify a person from your team in Quanta. What I say=
 is=20
that we should not have two mutual exclusive ways how to identify team=20
members. This is confusing for users.=20


> > Will it be documented? I could not find
> > any documentation for the annotations yet.
>
> Yes (according to my plans).=20

Very well.


> But I cannot document something that:=20
> - is not complete (and may change a little)
> - is only partially finished

Sure and I did not complain that it is not there. I just wanted to know if =
it=20
is on your todo list.

Jens

--nextPart1939657.cKe4FIjElK
Content-Type: application/pgp-signature

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

iD8DBQBDCplckYmIVB8IV+ARAicGAJ4iBm7KetX8xM7ShIgCiwkmbEE+gACgoH3T
ia85GcGbbvZiy3iGlKYfn00=
=Hdse
-----END PGP SIGNATURE-----

--nextPart1939657.cKe4FIjElK--

--===============1127420436==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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

--===============1127420436==--