Re: [Evolution] Problem viewing calendars on multiple machines

On Wed, 11 Mar 2009, Pete Biggs wrote:

Ummmm... no offense, but just looking at your instructions for changing
machines makes me think that the design of evolution is a bit insane.  I
really don't feel like what I want to do should be that difficult.  I figured
since evolution is the default calendar for most linux systems, it wouldn't
be... well such a pain to work with on multiple machines.

The issue really is that Evo is a client program, it was never designed
to offer the data that it uses to other programs, it was designed to be
a consumer of data from elsewhere.

Okay, that helps me understand the problem a lot better.

As others have pointed out there *are* programs that will successfully
extract data from Evo and synch it with another data source, but they
mostly rely on having some external synch server - that can be a 3rd
party, or you could run a server locally, but it's not a 30 second job
to do.

If it is only calendars you want to sync, then I suppose you might get
some mileage out of playing with the calendar.ics files.  But as poc
said, you should definitely make sure that Evo isn't running when you
synchronise - and I'm sure the Evo developers would point out that the
consequences of playing with the .ics files in Evo's local store is

I tend to leave both my workstation and laptop running most of the time, so shutting down evolution to sync will be a bit of a pain. Moving to an online service may, unfortunately, be in my future.

I do have one question about all of this. I have created a number of different "On this computer" calendar and none of them are accessible from my laptop. However, there is one calendar, "Personal" -- which I don't remember creating- *DOES* appear on both machines. If I understood why this calendar can do this, I wonder if I could understand how to perhaps coax my other calendars to have similar behavior.

My other thought was having a bash script running that uses sed to somehow replace machine1 name and ID with machine2 name and ID and vice versa. Perhaps that's what was underlying the other suggestions, but it wasn't clear to me.

Thanks for the input!


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]