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

List:       kde-pim
Subject:    [Kde-pim] Reqs for reliable/extendable PIM in KDE
From:       Nick Papadonis <npapadon () yahoo ! com>
Date:       2001-12-11 16:40:01
[Download RAW message or body]

> 
Organization: None
X-Face:  01-z%.O)i7LB;Cnxv)c<Qodw*J*^HU}]Y-1MrTwKNn<1_w&F$rY\\NU6U\ah3#y3r<!M\n9
 <vK=}-Z{^\-b)djP(pD{z1OV;H&.~bX4Tn'>aA5j@>3jYX:)*O6:@F>it.>stK5,i^jk0epU\$*cQ9
 !)Oqf[@SOzys\7Ym}:2KWpM=8OCC`
Date: 11 Dec 2001 11:40:01 -0500
In-Reply-To: <16DoMD-0fgpjEC@fmrl07.sul.t-online.com> (Ingo Assenmacher's message of \
                "Tue, 11 Dec 2001 15:56:25 +0100")
Message-ID: <m3elm190da.fsf_-_@localhost.localdomain>
Lines: 53
User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.4 (Civil Service)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Ingo Assenmacher <ingo.assenmacher@post.rwth-aachen.de> writes:
> > I was basically asking if you would design a database schema for the
> > KDEPIM project as a whole.  Lets say each package maintainer
> > collaborates about data storage informaiton with you.
> 
> Thanks for explaining. Yes, I would think that this would be a good solution.
> I would have to go into details of several packages. 
> Right now (being on the low-level of information here), I do only think of a 
> wrapper schema to conserve originally used formats (like: enhance data with 
> meta-information (user/creation date, whatever) and put in the original data 
> as a blob. 
> As almost all data is acessed via interfaces (is it?), this could be an 
> approriate solution. BUT: I have not gone into details here, and this is only 
> a very early idea.

Ingo,

I would think designing a schema and API a start.  Someone who
understands how data is stored and retrieved in the file format could
write a converter.  I don't think this is high priority for anything
other then calendar data.  

I know I'm starting from scratch data and would like to focus on
synchronization and hardware issues.  Conversion is low priority for
me.



Anyone needing mentioned subject,

Do you think its a good time to start splitting off on seperate
projects?  Maybe we could have interested parties organize each and
merge in a few months?

How much of Ksync is implemented?   I would be interested in helping
here.  Ingo seems interested in an information storage library.
Anyone else have any pieces they could drive?  

The core items to get an equivalent features of Outlook in KDE are (in order of
dependency, most dependent listed first):

- Information storage libraries/api implemented
- Ksync libraries/api implemented
- Palm plugin for Ksync
- Calendar/Todo plugin for Ksync
- Notes plugin for Ksync
- Something to get data from group scheduling emails to use
information storage api. 

Any comments?

-- 
Nick
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim


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