maemo.org - Talk

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar (https://talk.maemo.org/showthread.php?t=40408)

jcompagner 2010-02-23 08:07

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
are you also going to push it to extra-dev repository?

lorelei 2010-02-23 10:28

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Quote:

Originally Posted by jcompagner (Post 542241)
are you also going to push it to extra-dev repository?

At a certain point yes, it will be pushed to extras-devel. I'm still unsure if I it will be pushed already for this release or if I will wait for the next release.

The fact is that the upcoming release is not feature-complete (it will miss recurrent events synchronization and birthday calendars support), so I don't feel comfortable with submitting it to extras-devel in this state...

feydrutha 2010-02-23 16:06

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Quote:

Originally Posted by lorelei (Post 542393)
At a certain point yes, it will be pushed to extras-devel. I'm still unsure if I it will be pushed already for this release or if I will wait for the next release.

The fact is that the upcoming release is not feature-complete (it will miss recurrent events synchronization and birthday calendars support), so I don't feel comfortable with submitting it to extras-devel in this state...

I guess it depends on what your expected timeline is (difficult question, I know!)

Lack of features is not a reason to reject an app in the testing qa process, so long as the app summary is not creating wrong expectations.

If the next release will be in a week or two, it's probably not worth going through the qa process twice. Still, getting a version in devel may increase the amount of testers you get. If the next release will be in months, then an incomplete app may be better than nothing for a lot of people.

petibub 2010-02-23 21:28

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Hi Lorelei,

Glad to see that you're coming forward with the implementation. I have no problems if you change the format of the database. I can hardly await the new version :-)

lorelei 2010-02-23 21:58

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
I may go with a two-step process:

release the upcoming and feature-incomplete in extras-devel (and only there), so that I can also test out the auto-build process. That release will live for a few weeks (and won't be pushed to extras-testing), after that a new release with last few missing features will be added to extras-devel.

It will be that release that will go to extras-testing for the QA beating :)

As you said, expected timelines are difficult to deal with (especially with developments done in spare time), but once the big features are done, everything will go more smoothly, at least that's my hope.

econan 2010-02-23 22:18

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Thanks for great program. This is exactly what I was looking for. I have a question though. What is the challenge for not being able to sync repeating events? Is there an incompatibility/conversion issue?

Maybe I can spare sometime to help you fix this.

lorelei 2010-02-23 22:36

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Quote:

Originally Posted by econan (Post 543378)
Thanks for great program. This is exactly what I was looking for. I have a question though. What is the challenge for not being able to sync repeating events? Is there an incompatibility/conversion issue?

Recurring events are not really a challenge per se (thanks to the limitation of N900 calendar...see below). In fact it's just a relatively easy piece of code to be added. I left it behind for the moment because I wanted to have a stable solution for simple events first.

The only problem I can foresee: the N900 calendar program is very limited with recurring events: you cannot insert exceptions in a recurring rule, so recurring events with exceptions transferred from Google to the N900 will not reflect the real state of the calendar. This is the only issue I see so far.

dvergin 2010-02-24 06:37

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Quote:

Originally Posted by lorelei (Post 543409)
The only problem I can foresee: the N900 calendar program is very limited with recurring events: you cannot insert exceptions in a recurring rule, so recurring events with exceptions transferred from Google to the N900 will not reflect the real state of the calendar. This is the only issue I see so far.

What about the official calendar program not supporting "every second Thursday of the month" type recurring entries (which I find FAR more common than "the 14th of every month")?

GPE Calendar can do that (and exceptions). Does Erminig-NG support GPE Calendar, or do you plan to do so in the future?

lorelei 2010-02-24 10:04

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
Quote:

Originally Posted by dvergin (Post 543809)
What about the official calendar program not supporting "every second Thursday of the month" type recurring entries (which I find FAR more common than "the 14th of every month")?

hmm, I still have to dig more into that, so I cannot give you a definitive answer yet. Let's say that the preliminary tests I performed showed big limitations with the official calendar program, but I haven't performed a fully systematical check of its capabilities yet (even though many useful fields and APIs are there, they seem simply ignored by the calendar program).

Quote:

GPE Calendar can do that (and exceptions). Does Erminig-NG support GPE Calendar, or do you plan to do so in the future?
In the first full-featured release of Erminig-NG there will be no support for GPE, however it has been planned since the beginning to support GPE in a later release, in order to merge the old Erminig capabilities with the -NG ones.

gregc2009 2010-03-02 21:39

Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
 
I am having an issue that I don't know if it is something I am missing or if something has a problem somewhere. This is my first time trying Erminig-NG. I made sure I had the dependencies covered and installed it per the instructions. I am able to do the initial sync in which it goes through the prompts to create Main locally, N900 on Google, cal_ti_calendar_private on Google, and Main on Google (there already is a Main though). I put a test event on the phone's calendar, and one in each of the Google calendar's (Main, N900, cal_ti_calendar_private, Main (second one)). When I do a sync (python2.5 erminig-ng), it looks like it is doing stuff, but there are no updated entries in the phone calendar or on Google calendars.

What am I doing wrong?

This is the output:
Code:

Nokia-N900-02-8:/home/user/erminig-ng-0.1.2# python2.5 erminig-ng
---------------------------------------------
NEW EVENT
INSERT INTO events (localID, googleID) VALUES (30, "o62i5s1ekbk1pj2bmohcpbl6v8")
---------------------------------------------
NEW EVENT
INSERT INTO events (localID, googleID) VALUES (31, "5ua4dbc3gmevo19e1ifga4e5ec")
NEW EVENT
INSERT INTO events (localID, googleID) VALUES (31, "41amcnp20modb6krqvvgo9prug")
---------------------------------------------
INSERT INTO events (localID, googleID) VALUES (29, "bcgnc49lgnfaajgba7bfjn0sk4")
INSERT INTO events (localID, googleID) VALUES (15, "fina1vdcbn5er7trotr2aet56g")
INSERT INTO events (localID, googleID) VALUES (16, "lsa28718gvkmkf36imu384dkkc")
INSERT INTO events (localID, googleID) VALUES (17, "2t09ljfhrcvqptrlo1q4ga02v0")
INSERT INTO events (localID, googleID) VALUES (18, "lu8qeoodo51ie0lek4jtmk7uk8")
INSERT INTO events (localID, googleID) VALUES (19, "ij19cep7pcns7ilghhqud41ddg")
INSERT INTO events (localID, googleID) VALUES (20, "k2ud4bhhltv08097nv7fb1iq94")
INSERT INTO events (localID, googleID) VALUES (21, "rk81moitsrdsn5qovgqujsi47c")
INSERT INTO events (localID, googleID) VALUES (22, "ocfs1eqvmj7m2kes74euts6hu0")
INSERT INTO events (localID, googleID) VALUES (23, "e88keo1phhqkd9q5ea8rodav1s")
INSERT INTO events (localID, googleID) VALUES (24, "vi10l5p21lcfabrv3pnj0rmeuc")
INSERT INTO events (localID, googleID) VALUES (25, "ckgvtgcjrglp28tkvq5v4uhceg")
INSERT INTO events (localID, googleID) VALUES (26, "v9720li7c4m7aivbrsip5g3hr0")
INSERT INTO events (localID, googleID) VALUES (27, "ujctoij6f9r1a1g1bbjlqubhbo")
INSERT INTO events (localID, googleID) VALUES (28, "mccu6ijnc90pmrgqkfp4qteit4")
INSERT INTO events (localID, googleID) VALUES (1, "94oe0sreiktaqrknt9kdff6nlg")
INSERT INTO events (localID, googleID) VALUES (2, "pqegbt2kg13qd1rgjroquaj1j8")
INSERT INTO events (localID, googleID) VALUES (3, "3m69pm2e7lb65p91iko6gkgbec")
INSERT INTO events (localID, googleID) VALUES (4, "e84g09pbudssnslb1300dridb8")
INSERT INTO events (localID, googleID) VALUES (5, "n3frivkiqd148pi137cjlrjbec")
INSERT INTO events (localID, googleID) VALUES (6, "qi2ub7simju2u1ukl9cn9o7v5g")
INSERT INTO events (localID, googleID) VALUES (7, "4hmcfcg3lbdrqokh4n79buf838")
INSERT INTO events (localID, googleID) VALUES (8, "814pvv7eivpl2vqhoe4dgvc4s0")
INSERT INTO events (localID, googleID) VALUES (9, "mh8a4um6qkkrol2ecs53rltpn0")
INSERT INTO events (localID, googleID) VALUES (10, "4itr35a5gp87qmmjhnbq74bckc")
INSERT INTO events (localID, googleID) VALUES (11, "coj7ck1rbsfem44vjslkrbflds")
INSERT INTO events (localID, googleID) VALUES (12, "capj3g7lov693co3ufech4bhbs")
INSERT INTO events (localID, googleID) VALUES (13, "o87jvler5lp0s603vqj2abmbj4")
INSERT INTO events (localID, googleID) VALUES (14, "f8nhnjk7a921fpjeo8i74tbhd4")
Nokia-N900-02-8:/home/user/erminig-ng-0.1.2#



All times are GMT. The time now is 15:33.

vBulletin® Version 3.8.8