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

List:       kde-core-devel
Subject:    Re: Known "showstoppers"?
From:       George Staikos <staikos () kde ! org>
Date:       2005-02-25 19:01:22
Message-ID: 200502251401.22507.staikos () kde ! org
[Download RAW message or body]

On Friday 25 February 2005 13:52, Reinhold Kainhofer wrote:
> George Staikos wrote:
> > On Friday 25 February 2005 12:12, Reinhold Kainhofer wrote:
> >> It's just necessary to start kmail, but it won't happen in a plain
> >> vanilla kde installation, only when the users set up an imap resource.
> >
> >   This is rather ridiculous.  There's no way around it?  At least could
> > it not
> > start KMail without showing a window and then immediately closing it
> > again?
>
> So kopete would start kmail, load the addressbook, close kmail. Then
> konversation would start kmail, load the addressbook, close kmail. Then
> korgac would start kmail, load the calendar, and close kmail. And maybe
> korganizer is started by the session management, so kmail would be started
> a fourth time, and quit immediately afterwards. This just doesn't make
> sens.

  It does make sense, but the solution is clearly more complicated than the 
developers are willing to implement at this time.  For instance, having the 
ability to read this data out of the kmail cache, or having a centralized 
process (that for instance terminates after x minutes of inactivity).  There 
are lots of solutions.

  As it stands, this is a heavy penalty that kdepim imposes on KDE.  Do the 
DAV resources suffer the same problems, or is this purely IMAP resource 
specific?

> And any change to the data also needs to start kmail, because kmail is used
> as the storage backend of the imap resources...

  That's not so unexpected.

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/
[prev in list] [next in list] [prev in thread] [next in thread]