As far as technical details go, we're going to set the helper library up
in SVN at src/target/OM-2007/openmoko-libs/libmokopim. The library will
be called libmokojournal, to indicate it's the journal access library
for the phone.
Of course, we can always change this at a later date if anyone has any
objections. Once we have the relevant directory structures in place, we
will start writing the helper functions. After that we can start
deciding on what API we want to export. Suggestions on use cases and
possible API are still welcome now of course.
Regards,
Thomas
Thomas Wood wrote:
Werner Almesberger wrote:
Thomas Wood wrote:
* Search Use Cases
[...]
- Last 10 entries for Person
I hope you mean "N" :-) E.g., when I call a person, I may want to be
able to quickly retrieve all relevant communication, no matter how old.
("Do you remember the address of that restaurant we went to last time
we've been in Madrid, some three years ago ?")
This was a couple of example use cases, not an exhaustive list.
In reply to the rest of your e-mail, most of what you have suggested is
possible, or already provided by, our suggested implementation. The
calendar component of Evolution data server stores it's data in the
standard iCalendar format, so it would also be trivial for third party
applications to process the data (although we will be adding a few
custom fields). There are also already solutions to synchronise e-d-s
(including the calendar component) using SyncML.
Regards,
Thomas
--
OpenedHand Ltd.
51 Great Brownings / London / SE21 7HP / UK
Tel: +44 (0)20 8819 6559
Expert Open Source For Consumer Devices - http://o-hand.com/
------------------------------------------------------------
