![]() |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
dreixel: point taken for the one-way sync. That's a good idea.
For the bug you encountered: yes it is ignoring recurring events, and I just checked the code: the recurring event detection is done before ever manipulating the date, so the problem is not there. In fact after re-reading the stack trace you posted above, the problem is located in the data feed we get from Google: for some reason the published date of the event is outside the allowed bounds of the time module of Python. If you are willing to perform a little modification of the code and post here the result it would be great. Essentially, edit the file ermini-ng and insert before line 302 (i.e. before the line that reads "cdate = iso8601ToTimestamp(e.published.text)" the following code snippet (respecting the proper indentation): Code:
print e.published.text If you don't want to do that, no problem :) thanks |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Hi Domenech,
Quote:
This is caused by the noexec attribute of the MyDocs mount point. (see http://talk.maemo.org/showpost.php?p...0&postcount=95) |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
dreixel: well in fact it's not the date of the event itself, it's the creation/publication date of the event that is problematic.
In any case, you are right that erminig should catch those cases and manage them properly. There's clearly a bug there. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Hi Lorelei,
thanks for the v0.1.1. I had some time to test it and hey, both thumbs up :) The calendars are created on google as they should be - even the names are correct now. The events are (almost) correctly synchronized, the recurring events are ignored. "Almost" because: the end date of the events is wrong: the new events on Google are one day shorter than the original events in N900. I checked the time zone and it does not matter - the bug exists even for whole-day events. Anyway, great job. And I like the new hildon.Note() thing - gives a little more feeling like GUI :D What about the roadmap for recurring events? Having that I could start using Erminig-NG on a regular basis with my real calendar, which would be really coo :rolleyes: |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Quote:
but again don't quote me on that estimation: I'm notoriously bad at this game... |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
I'm using 0.1.1 and all works great and as expected. Thanks!
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Still using old version, but I believe the below isn't changed in the later release (correct me if my assumption is a mother). Until now, the thingy has been doing what it's supposed to do.
Code:
~ $ cd erminig-ng-0.1.0/ /P |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
To debug this: - If the problem is the one I'm thinking about, the problem is now persistent for you, right? (i.e. at every invocation of Erminig you get the same message?) - could you please follow the following steps and post here the result: - from the terminal, run Code:
sqlite3 ~/.erminig.db Code:
select * from config; |
All times are GMT. The time now is 06:44. |
vBulletin® Version 3.8.8