On So, 2011-03-27 at 03:25 +0100, Dinesh wrote:
I have had a week of holidays last week, so fixed a few little
in syncevo , which includes adding all the custom fields, fixing an
autotools problem, and started the work on the GUI myself. I have
tested it against the Ovi servers,
and here are the current problems:
Let me suggest a different approach: instead of talking about the
1. merge your SyncEvolution changes into master
2. include it in the nightly testing
3. then discuss the problems as they appear in the publicly visible
log files (http://runtests.syncevolution.org
Can you prepare a patch series that targets the current master branch?
Please keep my initial patches unmodified (expect for rebasing).
Split up the changes into self-contained pieces as much as possible,
with explanations of what each piece is about (problem, motivation) and
how the problem is solved (overview, details in the code).
Then I merge as appropriate and set up the testing.
Apart from this, what is remaining is adding support for KJots as
Memo Application of the KDE PIM.
in here, the issue is the data is of the format:
So how do i approach this ?
Overriding AkonadiMemoSource 's insertIem and readItem, to do the
necessary conversions (something like a bijective function mapping the
content of KJots item to VNOTE type ? ) vs. some other method like the
vcard field lists conversion (if so, please elaborate) ?
It would be simpler to ignore VJOURNAL. The "native" text format
expected by the Synthesis engine is plain text, with the first line
reserved for the Subject.
So you would have to parse what you get from Akonadi and compose a
string, which you return in readItem(). The configuration of that source
must define plain text as its format, in contrast to other note backends
which define VJOURNAL. insertItem() then does the inverse.
also is the vNote depricated or something and should vJournal be
in it's place?
As far as iCalendar is concerned VJOURNAL is the way forward, but I
don't know what KDE is going to do internally.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.