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

List:       kde-pim
Subject:    Re: [Kde-pim] [PATCH] iCalendar object comments
From:       tomas pospisek <tpo2 () sourcepole ! ch>
Date:       2003-08-21 21:13:37
[Download RAW message or body]

On Sun, 17 Aug 2003, Cornelius Schumacher wrote:

> On Wednesday 13 August 2003 21:10, Mark Bucciarelli wrote:
> > The attached patch adds the ability to read and write comments with
> > iCalendar objects.  The COMMENT attribute can be applied to a
> > JOURNAL, TODO, EVENT, TIMEZONE, and FREEBUSY object.   The COMMENT
> > tag can appear zero to many times.
> >
> > I put it the comment attribute in incident base code, but I'm not
> > sure if this is the right place.  An ALARM is the one iCal object
> > that does not allow a COMMENT attribute.
>
> Alarm doesn't inherit from IncidenceBase, so putting it there is
> perfectly ok.
>
> > By the way, this is how I have KArm currently storing comments.  I'll
> > back that out to use the DESCRIPTION attribute until I hear whether
> > this patch gets in or not.
>
> What does KArm store in the description, if comments are stored in a
> COMMENT property?

Um - Mark - I'd think the comments should go with the events that are
associated with a task. That means each time you work on a task you can
add a comment saying what you were doing. And if we go by such semantics
then we don't need any additional field - we can just put the comments
into the event description.

Text that is directly associated with a task itself can well go into a
task's (VTODO) description.

Am I missing something? Could otherwise explain what your intention
with the comments is?
*t

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]