Re: [evolution-patches] Support for XML in the save-calendar plugin
- From: Philip Van Hoof <spamfrommailing freax org>
- To: Not Zed <notzed ximian com>
- Cc: Joe Shaw <joeshaw novell com>, asdf <evolution-patches lists ximian com>
- Subject: Re: [evolution-patches] Support for XML in the save-calendar plugin
- Date: Tue, 14 Dec 2004 03:01:08 +0100
On Tue, 2004-12-14 at 09:18 +0800, Not Zed wrote:
> On Tue, 2004-12-14 at 00:13 +0100, Philip Van Hoof wrote:
> > On Mon, 2004-12-13 at 17:50 -0500, Joe Shaw wrote:
> > > You might be interested in the ical RDF work here:
> > >
> > > http://www.w3.org/2002/12/cal/
> > >
> > > It's similar to the standard RFC 2445 syntax and yours here so I don't
> > > think it'd be significantly more work, and would probably be preferable
> > > to creating a new syntax.
> > Indeed. It's not hard to support this RDF-format using the xml-format.c
> > implementation I've created.
> Would it be better not to add another format though? I think it would
> be unwise to add more subtle variations particularly if an existing
> standard will cover it.
Yes. Therefor I think it's wise to remove the xml-format.c after
converting to the RDF-format is completed.
> > I will probably implement it in rdf-format.c (and I will probably just
> > remove xml-format.c as with this rdf-format it's no longer really
> > interesting).
See :-)
> I'm not a calendar developer, but i wouldn't think it would make sense
> to support an interchange format internally.
Okay. But is support for exporting to this format desired or is also
that a bad idea? In my opinion you are right when you say that
supporting multiple formats internally is a bad idea. But as a user I'd
like the possibility of exporting my Evolution-data to other formats.
Using the new plugin-architecture, you can delegate that part of
Evolution-development to non-core development. Making it (more)
maintainable to have such a large set of features.
> They serve very different purposes. We have 'importers' that should
> import whatever this thing exports though, but the current importer
> framework is messy.
> I'd also highly recommend not creating your own xml format - if one
> exists that will serve the purpose. I don't know, for example, what
> kolab uses for its xml format, and if it is just another
> representaiton of icalendar itself.
Agreed. The current xml-format.c is of course just a tryout. I will
probably convert it's format to RDF sooner or later. If such export
functionality is desired of course.
--
Philip Van Hoof, Software Developer @ Cronos
home: me at freax dot org
gnome: pvanhoof at gnome dot org
work: philip dot vanhoof at cronos dot be
junk: philip dot vanhoof at gmail dot com
http://www.freax.be, http://www.freax.eu.org
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]