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

List:       kde-pim
Subject:    Re: [Kde-pim] [PATCH] Korganizer Exchange 2000 Patch
From:       Cornelius Schumacher <schumacher () kde ! org>
Date:       2002-07-05 8:55:44
[Download RAW message or body]

On Friday 05 July 2002 10:19, Best, Jan-Pascal van wrote:
>
> Here's an status update on the exchange 2000 plugin:
> - Read appointments from an Exchange 2000 server.
> - Handle recurrent appointments (no exception handling yet)
> - Handle full-day events
> - Write a single event to the server. Only a few fields are written
> as of yet: start time, end time, alldayevent, free/busy, description,
> summary, location. Missing most ostensably is recurrence.

That's already quite a lot of functionality. Great.

> - Writing to the server always creates a new event on the server.
> The uid isn't checked, so even if the event is downloaded from the
> server in the first place, a new one is created when uploading!

Is there a workaround of this problem?

> Can somebody take a look at this so I can check it in, or should I do
> that
> anyway to make it easier for more people to take a look at?

I would say, check it in. Perhaps we should disable compilation by default for 
now, so that compiling kdepim doesn't need the latest kdelibs or add a proper 
configure check. We also need a way to disable plugins in KOrganizer, so that 
it isn't loaded for people not interested in talking to an Exchange server, 
but we can add this later. Another comment: some files doesn't seem to be 
readable by all. It would be good to fix the file permissions before checking 
in.

> For the longer term, I see three possibilities:
> 1. Keep it as a plugin.

That's the easiest one. As the plugin already exists, I think we should also 
keep it in the future.

> 2. Implement it as a Calendar, so that korganizer can work
> directly on an Exchange calendar. I'm not sure if korganizer
> and the Calendar framework are up to that, though. For instance,
> does korganizer walk through the entire calendar sometimes? That
> would be uncool on a calendar on an exchange server...

The framework definitely needs some work before we can smoothly integrate 
server-based calendars, but in the long term this probably is the way to go.

> 3. Implement it as a Konnector in the kitchensync/ksync framework.
> I haven't following the discussion about this, would that be doable
> now?

This would allow to sync a local calendar with an exchange server. Sounds like 
a useful feature, but I doubt that the syncing framework is ready for that 
now. Perhaps a feature for 3.2?

> Last question: is it possible to put the exchange plugin on the feature
> list for KDE 3.1/3.2/4.0?

The feature plan for 3.1 is already closed, but I don't think it's a problem 
to add the plugin for 3.1. This shouldn't break anything. We need a way to 
disable it by default though. The Calendar implementation would be a nice 
feature for 3.2.

-- 
Cornelius Schumacher <schumacher.kde.org>

_______________________________________________
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]