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

List:       kde-pim
Subject:    Re: Moving low-level calendaring code to own library
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2001-04-17 22:07:23
[Download RAW message or body]

On Wednesday 18 April 2001 11:27, Gregory Stern wrote:
> On Tuesday 17 April 2001 05:23 pm, Cornelius Schumacher wrote:
> >
> > This split would create a library with a nice C++ interface to
> > handle vCalendar and iCalendar data. It could be useful for all
> > applications, which operate on such data like KOrganizer, KPilot,
> > Kandy or command line tools for manipulating calendaring data.
> > Another application could be a calendar server implementation.
>
> What do you think about extending your idea to become the entire
> kdepim server.  This server would be able to handle DCOP calls for
> calender specific information and address specific information
> (specifically it could pass the ContactEntry class around for adding,
> removing, changing entries).  I would be interested in helping to
> write some of the address parts.
>
> Do you think it makes sense to merge these two seperate applications
> into one kdepim server?   I think it makes sense; minimize the number
> of servers running.  Thoughts?

What would have an addressbook and a calendar server in common? I don't 
think they would share much code. If the only reason would be to reduce 
the number of servers I don't think it is worth the hassle of tying 
together two separate applications.

-- 
Cornelius Schumacher <schumacher@kde.org>

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