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

I would love to see GUI.. I am one of those users that need GUI to install :-)

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

Some of the calendars have been added to my account by work and I believe can't be used on a non-work gmail account (the company i work pays google for gmail/calendar etc.).

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

hmmm, maybe ideas for how the GUI should look like (just a raw sketch)...

At the beginning I was planning to have the interface similar to the original Erminig (http://maemo.org/downloads/product/OS2008/erminig/), but I'm open to new ideas, provided they are doable :)

Another good thing to have, some kind of "standardized" test suite, in order to ease the testing of all the aspects of the calendar sync.

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

A lot of people use google calendar, yet also have an exchange account for work. If google calendar sync can be moved off exchange, then mfe can then be freed up to handle the exchange account.

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

Hi, is the fisrt time I write here.

¿What you need is maybe a calendar involving all kinds of events?

I'll create an account and a calendar on it with all kinds of events I imagine. When it's complete, I'll give you the link.

Thanks for this piece of SW. Good work

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

Should look good enough in Fremantle if it is "hildonized" but the design is not so important for me. First functionality, then a nice design :)

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

I get an ImportError for module utils.iso8601. Did I miss something?

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

Hmm, you are the second person reporting this, but I can't figure out what's wrong, since other users don't have that problem.

Which version of Python are you using? At least version 2.5 should be used (hence the python2.5 command line mentioned in the first post....)

Are you using Erminig on your device or in Scratchbox?

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

This is python2.5. I'm trying to use it on my device, and prior to it I've installed python-gdata.

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

the gpe calendar was (is) my preference on the n800. will the new erminig-ng you're working on be able to update that calendar as well? the desktop display of the fremantle calendar does not give me enough instant information

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

The first iteration of Erminig-NG will concentrate on Fremantle Calendar (by the way, what is its official name?), but most of the work done there will be reused to also integrate support for GPE Calendar. Ideally I would like to have it modular enough to easily target any calendar.

So, in short, the final goal is to have sync capabilities for both Fremantle Calendar and GPE Calendar, in that order.

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

I'm going crazy here. Been trying to add extras as I can't find python-gdata in my app. list. After mucking around for ages, I found out that PR1.1 adds extras automatically (called maemo.org in application list).
When I browse extras I can see python-gdata, but it does not show up in applist on the N900.
What am I doing wrong!

EDIT: Never mind, figured it out. testing will commence.

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

Any word on the progress of the GUI? I'm all but willing to brick my phone for this app.

This is currently my only complaint on the n900 (and the only thing I've even found worth posting about). Any news would be great.:D

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

does Erminig-NG also sync with gmail tasks?

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

Not yet. As far as I know, google does not have public API for accessing gmail tasks.

http://code.google.com/p/gdata-issue.../detail?id=987

Once google has a public API for tasks, erminig-ng will likely support it eventually. (lorelei: Don't interpret this as me volunteering you for this!)

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

Thanks for the reply.
How about the multiple (and shared) calendars in google calendar? Can erminig-ng sync all of them? What about contacts?

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

Yes on multiple calendars.

I've only skimmed over the code at this point and haven't actually tried it out yet, so I can't answer on the shared calendars yet (though I'm guessing yes).

No on contacts.

I personally want to see all of these supported (in addition to tasks) and plan to help making them all happen. I've been sorta waiting to jump in until after the next release so I can see how lorelei is wrapping the calendar-backend API for use from python. There are other little improvements I have in mind from skimming the code last weekend, like preserving colors from google calendars and preserving the read-only flag on calendars (not sure what happens at the moment if you add an event on your n900 to a calendar that is a read-only google calendar).

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

I am also dying to have this. I was even willing to build it on the phone itself, but unfortunately that failed.

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

Quick update concerning Erminig-NG (and to answer some questions):

- no tasks or contact sync for the moment. This is still not on the radar, since I prefer to put priority on calendar sync

- GUI: not done yet. Still working on the core functionalities first. Once those are pinned down, GUI should be pretty straightforward (famous last words)

- the second public release of Erminig-NG is unfortunately late. In fact I was ready to post it last weekend, but a last-minute bug creeped up during the sync of 500 events at once and needs to be fixed before I can publicize the code. I'm almost done, but the week days are a bit crazy with work, so I can't rush it out.

As a reminder: the second release won't bring any user-visible improvements over the first release. The main change is the fact that I'm now using the C++ API to access the calendars instead of directly modifying the database. The API doesn't allow me to perform a 1:1 mapping between the DB calls and the API calls, so some additional logic must be implemented for it to work as I wish.

Third release will see the implementation of the recurring events and the GUI. Depending on how it goes I may make separate releases: first one with recurring events and then one with GUI (or the other way around).

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

Are you replying in the correct thread? As far as I know, installing the prerequisites for Erminig doesn't pull qt4 stuff. So far only python2.5 and python-gdata (+ dependencies) are pulled.

Next release will ask users to also pull in python-hildon for initial support of GUI, and there only GTK stuff is concerned and no qt at all.

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

You right, sorry. Never mind.

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

Any chance this means that an update for Erminig for Diablo is in the works? It already is a great little ap, and I appreciate your efforts in making it work as well as it does, but a guy that can't afford to upgrade their tablet can always hope. . . . .

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

Yes, it is planned to have erminig-ng ported over to Diablo, with sync capabilities for GPE. This should at the same time bring GPE sync to Fremantle.

Most of the work on erminig-ng will prove to be beneficial to erminig on Diablo, since It's a complete rewrite, which I hope will help me squash most of the annoying bugs of Erminig for Diablo.

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

I am the third with the utils.iso8601-problem :-(

Any Ideas?

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

I'm able to reproduce this problem only in the scratchbox development environment, if I use python instead of python2.5. On my actual device python and python2.5 commands behave the same (same version).

What is the output you get when you run the python2.5 command in an x-terminal?

Furthermore, what's the output of the following command?

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

Dear all,

Here's the second pre-release of Erminig-NG (version 0.1.0).

This post may seem very similar to the original post of this thread: it is indeed, but please read it carefully: there are some important changes!

It's still in alpha stage: so the usual recommendations stand:

BIG FAT WARNING: this is still alpha-quality software, so it's not really for those people who are afraid to lose events in their calendars!


No GUI available for the moment: next release should bring the GUI (at least that's the plan). And no .deb either: next release, when it will be a little bit more consumer-friendly.

As usual, try it on non-important calendars first, since we are not guarded against data loss.

Changelog (since version 0.0.1):

• All accesses to the Fremantle Calendar are done through the official API (no more direct access to the sqlite databases). This is the correct way of doing it, at the expense of a small C++ shared library to interface Python with the CCalendar API.
  
• When performing the initialization of the calendars to be synced (with the --sync-calendars option), a GUI dialog pops up to ask you if you want that calendar to be synchronized. This is to avoid problems with diacritics in the terminal.

Software dependencies: python-gdata and python-hildon (both of them available in Extras). By installing those two packages, all necessary dependencies will be pulled automatically.

How to install Erminig-NG

Download (link at the bottom of this post) and unpack the archive file somewhere on your device
Open the file erminig_conf.py and change the first three variables. They represent your Google username and password, and the full path to the root directory of Erminig (this is needed for the dynamic loading of the C++ library)

How to run Erminig-NG

For the first run:

This will ask you which calendar (both local and remote) you want to keep in sync

WARNING: For the moment it is important to run Erminig-NG for the first time with the --sync-calendars option, otherwise it will miss old events to import (known bug). Similarly, adding calendars to sync after the first real sync will miss old events (only new events from the time of the last sync will be synced in the the new calendar). Uhm, this is quite convoluted as an explanation...I hope that you will get the essence of this warning though :)

This will perform the bulk of the work and keep in sync the calendars. This is the command you want to run when you wish to synchronize your calendars.

If you added a local or Google calendar, you may want to rerun Erminig-NG with the --sync-calendars, so that it will ask you if you want to sync the newly discovered calendars (with the gotcha mentioned above!)

Information for those coming from the previous version
The internal Erminig database has not changed since the previous version, so you can continue to use the already populated database, without erasing it.

"Roadmap"
If a serious bug creeps out during the development of the next release, an intermediate bug-fix-release will take place...so I'm just mentioning the big milestones:

• Next version will bring recurrent events support, Birthday support and first release of the GUI. This will also be the first release with proper packaging. This version will also sport a modified database schema. I will try as much as possible to offer an update path to those who are already running Erminig-NG, so that you won't have to resynchronize everything.
• Next version + 1: Add support for GPE calendar, and hopefully backward compatibility with Diablo

FAQ (mostly copied from OP, but with some additions)

• There's a bug, what should I do?
  Two options:
  
  - report it in this thread, if possible by providing accurate step-by-step instructions
  - Contact me by mail: lorelei@garage.maemo.org (again with accurate instructions)
  
  In the future I will open a bugs.maemo.org component for Erminig-NG, in order to keep track of everything, but first I want to see how it is received within the community before investing resources that are not mine (i.e. maemo.org's bugzilla)
  
• Should I synchronize the local calendars called "cal_ti_calendar_synced" and "cal_ti_calendar_private"?
  cal_ti_calendar_private is in fact the default N900 calendar (which may have another name). It is safe to synchronize it. The other one I still don't know.
  
• What about birthdays?
  Even though Erminig will ask you if you want to synchronize the birthdays, nothing will happen if you accept. This is a side-effect of using the C++ API. There's still no code on Erminig's side to manage the birthday syncs.
  
• I have troubles with a missing import (xml.utils.iso8601)
  You are affected by this bug if Erminig-NG crashs at startup with the following message:
  
  Code:

  ---

  Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named iso8601

  ---

  Please see this post with an updated erminig-ng release that specifically fixes this problem:
  
  http://talk.maemo.org/showpost.php?p...7&postcount=93
  
  
• I would like to reset Erminig-NG to a known state (i.e. a state where it doesn't know anything about calendars relationships)
  Remove the file ~/.erminig.db
  This will make Erminig-NG going back to "factory settings"
  Please note that this may generate duplicate events in Google or Fremantle Calendar if you perform a resync on calendar previously synced.
  
• What is the stability status of Erminig-NG ?
  It's in early alpha stage. I'm just starting to pin down the basic functionalities before moving on the the GUI part
  
• What about sync conflicts (modification of an event both on Google and on the local calendar)?
  There's no explicit handling of conflicting updates for the moment. This will be addressed in a future version
  
• Why no .deb package (or why not in Extras-devel)?
  Erminig-NG is still in early development phase, so by publishing only the .tar.gz I will try to "scare away" people who is not comfortable with command-line. This is for your own good. Don't blame me (or maybe yes). Proper packaging will come in its own time.
  
• What works, what doesn't work?
  So far, I can tell for sure that recurrent events don't work. It's not a bug (yet): it's simply not implemented yet. This will be supported in the future.
  
• How does this relate to Erminig (not -NG?)
  I'm also maintaining Erminig (two-way sync between GPE calendar and Google Calendar), and Erminig-NG will eventually replace it. It is planned to support both GPE and "Fremantle-Calendar". By rewriting Erminig from scratch I will be able to eliminate a lot of unused code in Erminig, and this will allow me to understand more in details how Google Calendar works (please remember that I'm not the original author of Erminig, I just picked up the development. Erminig-NG on the other hand will be essentially a clean-room reimplementation of Erminig)
  
• I would like to recompile the C++ layer
  Feel free! Here's the command line I'm currently using in Scratchbox:
  
  Code:

  ---

  g++ calaccess.cc `pkg-config calendar-backend --cflags --libs` -shared -o libcalaccess.so

  ---

Feel free to drop me a message if you find a bug (or just if you find this piece of software useful): those are always appreciated!

Download of erminig-ng 0.1.1 is available in this post:

http://talk.maemo.org/showpost.php?p...7&postcount=93

it fixes the iso8601 problem a few users had. I've removed the original 0.1.0 release, since it was bugged!

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

Hello all,

lorelei, I want to thank you for this fantastic job. I was really missing Google Calendar sync in my n900 and I was thinking about writing myself a little one-way-sync python script until I found this thread.

One question, though: it is possible to sync my N900 main calendar (called "N900" in my phone) with my main calendar in google?
What I mean is: I don't want a new "N900" calendar in google, I want to sync it with my main calendar there.

Thanks again for this nice app :)

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

This is not possible yet, however the next release with the GUI will allow that.

I did not offer this possibility in this text-only release since it's not easy to come up with a user-friendly way of asking the user to do the calendar associations. With a GUI, the problem is easier to manage, hence the non-implementation for the moment.

Thank you for reminding me that I have to implement that :)

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

Thanks lorelei!

For those who previously asked about shared calendars, the answer is currently no. However, a simple change from GetOwnCalendarsFeed() to GetAllCalendarsFeed() in the file erminig-ng will allow you to sync shared calendars as well.

As mentioned in my previous post, erminig-ng does not preserve the read-only status of calendars, so I'd expect breakage if you modify shared read-only calendars on your device.

I'm hoping to find time in the next week to look at preserving the read-only flag and colors from the google calendars. I'll submit a patch here if I do!

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

tuxfoo: thank you for the pointer to GetAllCalendarsFeed(): I kinda overlooked that possibility.

Upon inspection of CCalendar API, it's possible to flag a N900 calendar as read-only, so that should do the trick. I just have to figure out how to get the same information from Google Calendars, but I suspect that it won't be too difficult.

Concerning the colours, unfortunately the N900 palette of colours available to the calendar is quite limited (ten colours or so), whereas Google's palette is a bit more extended, so it won't always be possible to have a 1:1 matching between the two.

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

Here are the screenshots: http://akkimoto.blog.de/2010/01/31/p...relei-7912754/

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

Right, I think this would be trivial.

Your right. When looking over the calendar-backend API previously, I noticed you could specify the color for a calendar. I had just assumed this was more flexible, but the enum in CCalendar.h does only define a small palette. We could try to match the closest color, but it might not be worth the effort. It'd be much better if calendar-backend took at RGB color.

Anyway, keep up the good work!

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

It's caused by line 32 in erminig-ng: "import xml.utils.iso8601"
The python-xml package is installed on my machine, and the utils/iso8601.py file is there, but the error still occurs. Reinstalling python-xml did not help.

Anyway, python-xml has to my knowledge not been maintained for ten years or something, and is removed from later versions of python distributions. So you might consider using some other module for the 8601 stuff.

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

The same as when typing just "pthoyn":

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

Changing the line from "import xml.utils.iso8601" to "import papyon.util.iso8601" made it work.

/P

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

I agree that python-xml is unmaintained for quite a long time and that it's gone in newer version of Python.

This however doesn't explain why for some people it doesn't work as expected (which is kinda enraging because there's no logical explanation yet).

I may end up doing what you suggest, i.e. use another module for ISO8601 dates...

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

hmmm, this is interesting. papyon is part of one of the many MSN implementation for maemo, and maybe it's conflicting with python-xml (I'm betting that python-papyon is problematic here).

In fact I don't have any MSN client installed, so this may be the problem:

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

Palleman:

would you mind posting here the result of the following two python lines (executed on your device, in a Python shell):

I suspect that papyon's version of iso8601 takes precedence over the version from python-xml, which in turns causes us some griefs.

thanks

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

Sorry, I was a bit fast there. It didn't make it work, it just made the error disappear. I added a Google calendar loaded with entries, and ended up with a new but empty calendar on N900.

I.e. the first --sync-calendar command is supposed to fill it up with the existing entries, right? I don't want to run the second command yet, don't want to end up with an empty calendar on the Google side too.

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