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

List:       kde-pim
Subject:    Re: [Kde-pim] Request for kdepim/korganizer
From:       Mark Westcott <mark () houseoffish ! org>
Date:       2001-10-23 10:43:38
[Download RAW message or body]

On Tuesday 23 October 2001 8:02 am, you wrote:


Thanks for your feedback!  I apologise for my use of the 'u', but it was 2 
o'clock in the morning and I was feeling rather lazy.  I'm glad that you 
'enthuse' of the idea,  and agree on your comments.

I have a small amount of knowledge of C++ and an even smaller knowledge of 
KDE, but I shall do my best - its just that I downloaded the source tree of 
kdepim and it looked a little scary!  I may need some help along the way, but 
I shall see what I can do.

I'm just thinking about where to store this added information -  a new 
relational database?  A field in the address book database wouldnt work as it 
would only allow for one thing to be 'pinned' to it.  

So I think a field in both the email and contact databases showing that there 
is data 'pinned' to it, with an identifyer that was the same as a value in 
the new database telling it what that info was and where to find it?

This is quite a big thing to do, I now reliase.  For example, what happens if 
someone deletes an email which is part of a TODO?  An error should be flagged 
up etc.

A new library to handle it all perhaps? This would mean all parts of the 
kdepim suite could use it


Mark

> Hi Mark,
>
> On Tuesday 23 October 2001 02:29 am, Mark Westcott wrote:
> > I dont know if this is the right place to do this, but there is something
> > I would very much like implemented in kdepim/kmail/korganizer.   This  is
> > followups, which are truely brilliant if anyone has used Outlook.  These
> > are basically alarms linked to either contacts or emails.  So you can
>
> First off, let me enthuse about this idea. It sounds really neat, and if I
> may be bitter it seems typically MS-ish to limit it to emails or contact
> info. A much more general system of linking any content to an address would
> be so much more useful: Phone John and ask him about this document should
> be able to pop up John's contact info, a KNote about him (ie. handling
> instructions) and the KWord document you need to talk about. Consider it
> "paperclipping" stuff to the appointment.
>
> > create a follow up on a contact saying 'Phone James' and when you see the
> > alarm you click a button and the contact shows up with the phone number,
> > or u can autodial etc.
>
> [I think the use of the non-word "u" is starting to take epidemic
> proportions, (what do you think a u-turn means?) that's for sure.]
>
> Autodial is slightly frightening on a multi-user system, but through a
> little DCOP scripting I'm sure kppp could be convinced of the same (oh,
> wait, you want to *talk* to him?). Another neat idea: a general DCOP
> scripting widget where you can fill in app, iface, function, args of a
> *sequence* of DCOP calls and have them execute. A boon for scripting
> viruses, I'm sure (kmail KMailIface send everyone /tmp/k3w1dc0Pskr1p7).
>
> > What do you think?
>
> So now I've enthused above, I get to rain on your parade as well. If I may
> be highly ungenerous, it's just Cornelius and me who do "the gruntwork" of
> coding around here. If we tried to do every cool feature request that
> arrived on our desks, we'd be at it full-time. To me it seems that
> Cornelius *is* at it full time, but I know I'm not. So "just an idea" isn't
> enough -- it helps a lot if we have a mockup to look at, or some
> screenshots with the feature doodled in, or best yet ..
>
> 	send patches!
>
> Seriously! Even if you can't code now, you could learn and then lead a
> useful and productive life afterwards. This sounds like a big complicated
> thing to get started with, I'd probably suggest starting with figuring out
> what you want the UI to look like and then working on code just for that. A
> little push *can* move us a long way.
>
> [ade]
_______________________________________________
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]