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

List:       kde-pim
Subject:    Re: [Kde-pim] Contact Pinning Patch
From:       Adriaan de Groot <adridg () cs ! kun ! nl>
Date:       2001-12-07 10:00:06
[Download RAW message or body]

[Here's the reply to the pinning-stuff I promised Mark I'd write when I
wasn't drunk anymore.]

On Wed, 5 Dec 2001, Cornelius Schumacher wrote:
> > Firstly, I will modify my code to include your comments.  No problems
> > there. Secondly, the motivation for this patch. Firstly, say you want to
> > phone Jim, he is not actually a _participent_ in the todo at all.  The todo
> > is completely yours, its just that another party is involved.
>
> If you have to phone somebody, he should participate in the phone call,
> shouldn't he? It might also make sense to send him the todo per email, so he
> knows that you plan to call him. I think this is a classic example for the
> use of an attendee.
>
> > As I said, this is only the first stage of my patch.  I just thought I'd
> > get the basic stuff in before anything else.  More which shall make it into
> > a more usefull feature will follow shortly.  Basically, I am trying to
> > implement something similar (but better, of course) not the follow up
> > feature in Outlook, which is hugely usefull:

Let's not forget that Mark's patch is a first step in a more generalized
pinning-stuff-to-appointments framework, where you can associate just
about any mimetype / file with an appointment. This would let you attach
the kword document the appointment is about to the apt. This does a lot
more for the "everything is PIM" idea that was bandied about on the list
months ago than any of the whitepapering we did then.

> > Say Jim phones you, and you arrange that you will call him back on Tuesday.
> > With my code, you will be able to select him in KAddressBook, select 'Todo
>
> I completely agree that this is a very useful feature, I'm just wondering if
> this also can be done by using what is already there without introducing
> completely new fields and GUIs. As contacts already can be associated with
> todos and alarms can execute arbitray programs, e.g. kaddressbook, I would

Mm, like "kword http://yourname.here.nl/importantdoc.kwd & kaddressbook
Jim & cdplay stop" ? Then its already a lot closer to a complete
implementation, I'd say.

[Note: it's pretty hard to find out what already exists and what doesn't
in a big project like KDE. THere was a long discussion about pinning on
the lists when Mark started, and this feature was never mentioned back
then. If I'd known about it, I'd have pointed Mark in that direction.]

> think that you don't need anything special to accomplish, what you want. Ok,
> you might need some extensions to the existing stuff to make it usable in a
> convenient way, but introducing new fields to the calendar format is
> something I would prefer to avoid, because it kills interoparbility.

Does it? I thought the X-whatever fields in a calendar entry were harmless
for applications that don't understand them. But I understand your concern
that then there's possibly important information in these fields that
isn't understood -- for example, people might pin attendees to a todo,
instead of setting them as attendees.

Hm. Where's that usability group when you need it?


-- 
+------------------------------+
| Adriaan de Groot             | Drinken, in een bepaalde tijd symbolisch,
| http://www.cs.kun.nl/~adridg | is in een andere tijd zuipen - Wittgenstein

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim

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