[Kroupware] Re: kroupware_branch: kdepim/korganizer

[Bernhard Reiter]

--Boundary-02=_WsS59Ejcy/YETnG
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

On Friday 08 November 2002 21:35, Cornelius Schumacher wrote:
> On Friday 08 November 2002 16:28, Bernhard Reiter wrote:
> > On Thursday 07 November 2002 16:03, Cornelius Schumacher wrote:
> > > KOrganizer aims at being a iCalendar compliant application.
> > > If it can't handle a file conforming to the standard this is bad.
> >
> > There will be many way to write an iCalender compliant files which
> > does not really make sense. For Kroupware a subset of the iCalender
> > standard is probably perferable.
>
> For Kroupware that might be true, but we are talking about the code
> which will be merged back to the main KOrganizer version.

Talking about how KOrganizer will handle this I'm not sure.
(The detailed merging strategy is up to the client guys, btw.)
Personally I think that KOrganizer could live with the interpretation
of one assignment per task and the simpler interface.
If necessary somebody could add option to enable an expert interface.
As regarding to iTIP KOrganizer might still be a conforming application
just not assigning one tasks to several people.

=46or the Kroupware GUI we had to separate the invitation dialog
to be different for tasks and events anyway. All events have a duration.
It might be possible to merge this and so that handling several attendees
for todos can be added later.

> > > What happens, if you read a
> > > todo with multiple attendees with the kroupware interpretation of
> > > todos? What happens, if the user edits it or removes the attendee?
> >
> > BTW: Does the iCalender format propose a workflow for all this?
>
> There are several long sections about scheduling todos in the iTIP
> standard (rfc 2446). This even includes detailed examples about todos
> with multiple attendees.

There are some examples but not enough to explain the possible workflows.
--Boundary-02=_WsS59Ejcy/YETnG
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQA95SsWh9ag3dpKERYRAuhgAJ9sbvfMaBYSBi+doeel01hu67VYGQCdFwA2
mCsOVLsg6HRGTko5gL9aQPY=
=zqMo
-----END PGP SIGNATURE-----

--Boundary-02=_WsS59Ejcy/YETnG--