On Fri, 2012-08-03 at 21:42 +0200, Ove Kåven wrote: > Den 02. aug. 2012 11:24, skrev Patrick Ohly: > > Either way, it's primarily lack of developer time for the N9 port which > > prevents adding support. > > Well, it's just a matter of modifying the KCalExtended backend, I > suppose. I've been thinking about it. If people encourage/pester me > enough, I might get around to it...
I hope you received enough encouragement and not too much pestering ;-} If you look at adding support for notes, then I suggest that you do it based on 1.2.99.x. When I added support for VTODO in the CalDAV backend, I changed the core so that a backend can exchange the notes as iCalendar 2.0 and let the engine do the conversion to plain text if (and only if) the peer needs it. That's more flexible and easier than the manual conversion to plain text as (still) done by the EDS backend. See the following commits for details: commit 16e0b4af191fda9c4d2a8f981d5c2513fb818d11 Author: Patrick Ohly <[email protected]> Date: Fri Jun 15 12:09:07 2012 +0200 WebDAV: exchange VJOURNAL as iCalendar 2.0 or plain text Use the new "text/calendar+plain" type so that "caldavjournal" can be used with peers which do not support iCalendar 2.0 for memos. commit 92d7e7cc489b7251a122bf2b1eccec3fab6f576c Author: Patrick Ohly <[email protected]> Date: Fri Jun 15 12:07:46 2012 +0200 engine: support VJOURNAL and VJOURNAL+text/plain The "text/calendar" type now also contains rules for parsing and generating VJOURNAL in iCalendar 2.0 and vCalendar 1.0. When using "text/calendar+plain", the internal format is iCalendar 2.0 with plain text used as alternative if the sync peer does not support VJOURNAL for memos. These types can be used as "databaseFormat" of the file backend and by other backends which want to replace plain text as exchange format for memos. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
