Re: icalendar file sync
Armin Bauer <[email protected]>
| Newsgroups | gmane.comp.gnome.apps.multisync.user |
|---|---|
| Message-ID | <[email protected]> |
Markus Meyer wrote: > Hi Marco, > > the Mozilla Calendar plugin (plugins/sunbird_plugin), which you can > download from CVS works directly with .ics files. It can use both local > .ics files and files on a WebDAV server, and should be able to also read > and write .ics files from other applications. It is not 100% finished > yet, but I use it everyday and it seems to work fine. Of course you are > welcome to test it out with other applications' .ics files and report > your results. > > When the first version of OpenSync is released I will port this plugin > to the OpenSync API. At this time it should also be discussed if there > should be another name for the plugin, e.g. "ICS plugin". Armin > suggested to create two versions of the plugin, one specific to Mozilla > Calendar (which reads Mozilla Calendar's config files), and one for > arbitrary ICS files (which must be configured manually). At the moment > I'm more in favor of a single plugin which knows how to deal with > multiple applications, but can optionally be configured manually. > i think there was a misunderstanding :) I meant that it would be good to implement the ics file sync into a library (like the bluetooth library of the irmc plugin) that can then be accessed by other plugins. So there would then be a mozilla plugin that reads the mozilla config and uses this lib to sync the local ics file. And then there would be a caldev plugin that pulls the ics file from a webdav storage first and then syncs it. > One reason why a generic .ics plugin isn't high priority is that it is > always better to use a sync API than write to the .ics files directly. > For example, Mozilla Calendar will not update its display when the > underlying .ics file changes, you have to refresh it manually. Also, > there are synchronisation issues with server-based .ics files (WebDAV), > because Mozilla Calendar doesn't implement proper locking. So I see the > Mozilla Calendar plugin (= .ics plugin) more as a workaround for > applications that don't have a proper sync api yet. > i agree. but this cannot (and should not) be fixed in multisync. the question is when the sunbird people are going to implement a proper sync api. if it is in reasonable time there shouldnt be any need to create a plugin that reads mozilla's configs. > > Markus > > > Marco schrieb: > >> Hi >> >> Recently I found out, that lots of Calendar clients use an Ical file >> as storage. Or can at least work with this file type. I was wondering >> why nobody is writing a general Ical Multisync plugin. like this we >> can open that file with different calendar clients and don't have to >> worry about the application. >> >> What do you think about this? >> >> Thanks for feedback >> >> >> Marco >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Multisync-users mailing list >> Multisync-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >> https://lists.sourceforge.net/lists/listinfo/multisync-users >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Multisync-users mailing list > Multisync-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/multisync-users
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFCP+0mq9z7v9k9UakRAjCBAJ47oIDimXbOuMXR61vXlpAwekeuTgCdGMZV 7lPeVKvcz3A60qAtvvGO3lE= =XiKq -----END PGP SIGNATURE-----