On 06. aug. 2012 12:16, Patrick Ohly wrote: > I hope you received enough encouragement and not too much pestering ;-}
Maybe, but I was more concerned about getting periodical reminders if I work on it for a while, take a break, start doing something else of importance, and then something else, and so on, and forget all about it. > If you look at adding support for notes, then I suggest that you do it > based on 1.2.99.x. Yes, I was going to anyway, of course. (Though it turned out that the new code and build system took a heck of a lot of work to manage to build on Maemo. A whole weekend spent just on that, patching .cpp files that don't build with g++ 4.2, patching configure to check for missing headers and other stuff, debugging linking failures, and whatnot.) And just in case you want to know, I'll change the Maemo 5 backend a bit as well, to no longer use TrackingSyncSource, but do custom change tracking like the KCalExtended backend does, asking the database only for stuff modified since the previous sync, instead of always asking the database for everything. (I was always concerned about it always unnecessarily loading the whole calendar into RAM in listAllItems, so it was about time I fixed this. My personal calendar is probably not going to get smaller anytime soon, since I rarely delete stuff from it, so...) There's one question I have about the change tracking in KCalExtended. In beginSync, you ask the database for all modifications done since the previous anchor. In endSync, you generate an anchor based on the current time when endSync is called. Wouldn't this risk losing any local changes done by the user *during* the sync, between beginSync and endSync? Would it be safer to generate the anchor in beginSync, so if the user does anything during the sync, the next sync can catch it? > 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. Yeah, I thought about something like that already. I didn't want to assume text/plain, as the N9 shows the creation time of the notes, which might be hard to sync with the simple plaintext format. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
