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

List:       kde-pim
Subject:    Re: [Kde-pim] Kaplan: The road ahead
From:       udoh <udoh () pacbell ! net>
Date:       2002-09-18 21:34:17
[Download RAW message or body]

Mark Westcott wrote:

>On Wednesday 18 September 2002 8:42 pm, Daniel Molkentin wrote:
>
>>Moin!
>>
>>This is a status update on Kaplan development and a RFC at the same time
>>that many people have asked me fore to step forward in Kaplan Development.
>>I just wrote down some points and I am curious about your opinions.
>>
>>1) Kaplans general design
>>
>>At the moment Kaplan bases on an abstraction through plugins, that get
>>loaded on startup and hold some information about the Part to be loaded. I
>>would prefer if we could get rid of this cruft. All information we need can
>>be put in header files AFAICS.
>>
>>- Let KParts communicate directly
>>
>>I think this question is pretty much clear: If we can, we should use kparts
>>directly just like the kroupware guys do wherever possible. I think the
>>current design in the kroupware branch to move the functionality into
>>seperate classes might ease porting.
>>
>>2) Kaplans name
>>
>>I agree with you that Kaplan is not a real good name for a consumer
>>product. I agreed with Don to call it Kontact. We will switch the name at
>>some point but I consider other (design) decitions to have precedence.
>>
>>3) Configuration of the Parts.
>>
>>Do we agree that Kaplans Parts should store their config stuff into
>>kaplanrc when loaded as parts? How could a merged configuration look like?
>>I think Don did some researches in that area. Any news?
>>
>>4) Kroupware integration
>>
>>Ok, let's see what they have so far and who is in charge:
>>
>>- Offline IMAP:
>>That's obviously a KMail thingy.
>>
>>- Handling of incoming VCal Events and:
>>Cornelius should probably comment on that. Anyone?
>>
>>- The KOrganizer side:
>>Looks like we won't need to change too much, I am currently trying to get
>>kroupware_branch working to get an impression.
>>
>>- KAddressbook: Any strong feelings on the integration of the addressbook
>>(other than showing it?)
>>
>
>Yes, some way of linking notes, appointments, todos etc to a specific 
>addressee.  No idea how this could be achieved, other than the use of a pim 
>database, but thats unwieldy.  Any ideas?
>
>Mark
>
>
>_______________________________________________
>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/
>
How about using a database engine called Firebird. It is opensource and 
crossplatform.

Udoh


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