![]() |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
You have to run erminig-ng without any parameter to perform actual sync. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
OK, found a possible workaround that XML problem (by the way, thank you Palleman for putting me on the right track!).
Instead of importing xml.utils.iso8601, we can import _xmlplus.utils.iso8601 (and modify all references to the new import) a not-so-satisfying explanation can be found on this web page: http://www.amk.ca/diary/2003/03/pyth...plus_hack.html I have to make a few tests to see if it works as expected, but I'm fairly confident that this is the correct solution. I will update the FAQ immediately and prepare a new package (tomorrow, because it's a bit late around here :)) |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
I looked into our find results, and we both have _xmlplus in /usr/share/pyshared but you also have /usr/lib/python2.5/site-packages/_xmlplus/ which I don't. I added a symlink, and that made everything work. I changed the import line and all references in the file, deleted the .db file, reran the --sync-calendars and ran a bare erminig-ng. It is now adding events from Google to the new local calendar. It is slow and it's eating resources, but I guess that's what you get for running stuff that's not even in a .deb yet, and in addition doing it with a massive data source and output straight to the screen... |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
I've now tested adding and deleting events both ways, and it seems to work fine. No recurring events though (which is not only bad, since I won't have a couple of hundred birthdays duplicated).
Is there a way to fiddle with the .db to change the binding from the new calendar to the default N900 calendar? Or, is there a way to change which local calendar is the default when adding new events? |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
waiting for this bad boy. When can we expect a release with a GUI?
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
The main issue at the moment is that xml.utils.iso8601 stuff that is really worrying me since I can't find a proper pattern for the failure. I will probably install all the packages other people installed to see which one is causing grief.... |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
To those who are going to try the symlink to xml.utils.iso8601: please remove the symlink once a proper solution has been found! Creating such a symlink may have unintended side effects on other programs!
The proper workaround is in the works (probably by using another module), I hope to get it done by this evening. thanks |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
As always, the one typing the above is the one living with the consequences (although I haven't noticed any side effects so far). /P |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Quote:
Quote:
Quote:
Concerning the slowness: normally it's only the first sync that may be slow, since it has to fetch quite a lot of information from Google, all subsequent syncs should be faster. Concerning eating resources: do you mean memory resources or CPU resources? Memory usage at first sync increases in O(n), with n being the number of events, and more generally it's also O(n) in the subsequent syncs, but here n is the number of modified/new/deleted events (and not the total number of events) And yes, output of the debug data to the screen will not help. All that output will be removed in the next version, and only a few lines will be logged in an ad-hoc log window. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Regarding the xml.utils.iso8601: I will definitely abandon that module, since it's very problematic under certain circumstances.
I will use the dateutil module (additional dependency, but that package is available in Extra). This means that I have to publish another version before the one with the GUI, since as you can imagine date handling is quite critical in Erminig, so I want to be sure that there is no hidden surprise somewhere with that new module. Concerning the GUI: I will post a few screenshots of the mock-ups in the next few days. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Quote:
Subsequent syncs are also slow enough to have time to read the output, but since it's only a couple of events each time, it doesn't matter that much. /P |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
OK, here's a fixed version for the iso8601 problem. This is the only fix in this release, there's absolutely no new feature compared to 0.1.0.
Since it appears that python2.5-dateutil is not available in Extras yet (it's only in -devel), I've changed the strategy: I'm now bundling the iso8601 module together with erminig. This should fix once for all the problem. Once python2.5-dateutil is available in Extra I will change the code to use that module and get rid of the one bundled. I'm also removing the old release from the previous post and redirect here for the downloads. thank you for the patience and for the help pin-pointing the problem! Updated version of Erminig-NG can be downloaded here: http://talk.maemo.org/showpost.php?p...&postcount=128 Version 0.1.1 that was previously here has been removed, since it contained a bug. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Now I'm getting:
Code:
Traceback (most recent call last): |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
hope this helps! |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Thanks, that worked, but now I have other problem:
Code:
Traceback (most recent call last): |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
I will probably have to clip the dates after the maximum timestamp, since they cannot be managed correctly by Python... |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Also, I have a feature request. It would be nice to have a switch to perform only one-way synchronization (namely from Google to N900). This also makes it safer for users who want to make sure their Google Calendar will not be altered in any way.
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
I've tried your software and I receive the next error: Code:
File "erminig-ng", line 43, in <module> Code:
google_username = "my_username" |
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; |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Quote:
Looks normal to me. Running date "+%s" now gives 1265202655 What should I change it to? /P |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Could this be a problem caused by mixing local time and UTC?
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
the iso8601 is supposed to manage the UTC and local time conversions by itself, and I did my best to have all date/times in UTC.
In fact I think that Palleman's problem stems from the hack of creating a symlink to a iso8601 module provided by another package than python-xml. I would suggest to upgrade to erminig-ng-0.1.1, which bundles the correct module. If the problem persist, then I will ask you to perform some modification in the code to pinpoint the problem. thanks |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
/P |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
Let's try to debug it: Can you please add the following two lines in erminig-ng, at line 289 (just after the line that reads query.max_results = "100000"): Code:
print "updated_min=%s" % (query.updated_min) and post back the output? thanks PS: just to make sure: did you remove the symlink to iso8601.py you created? |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
As I promised a few posts ago, here are the first screenshots of the GUI for Erminig.
This is still a work in progress and a few things may change, but the general idea is there. Most of the sync functions of Erminig are not tied into the GUI yet: each thing in its own time :) You will probably notice that there's mention of syncing GPE and Contacts: just to make things clear: those functionalities are not implemented at all for the moment: I just provisioned the GUI so that I can extend the sync capabilities in due time! As usual nothing is set in stone: if you have any suggestion, I'm open to them, provided they can be implemented! Main window: http://imgur.com/c9eMM.png Google Accounts management (multiple accounts can be defined): http://imgur.com/PnrRX.png Start of the "Add new Google Account" wizard: http://imgur.com/wTeAv.png |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
|
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Is the "Google only" going _to_ Google only or _from_ Google only? Maybe you could change it to "To Google" / "To Local" (or "From X") instead? Or make some small blingy arrows to show the direction.
I'll put in your print lines later today and get back with results. Edit: I just noticed the source column.... anyway, those arrows could (apparently) avoid some confusion. |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
I will probably end up displaying (as you suggest) "From Google" and "To Google"... |
Re: [Announce] Erminig-NG: two-way synchronization Google Calendar <-> Fremantle Calendar
Quote:
What do you think about autosync and running in the background? Will it be possible to set a syncinterval? |
All times are GMT. The time now is 10:03. |
vBulletin® Version 3.8.8