RSS/Atom feed Twitter
Site is read-only, email is disabled

Archive based project storage with XML catalog

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.

Archive based project storage with XML catalog Øyvind Kolås 03 Mar 00:07
  Archive based project storage with XML catalog Boudewijn Rempt 03 Mar 11:15
Øyvind Kolås
2006-03-03 00:07:44 UTC (about 18 years ago)

Archive based project storage with XML catalog

My toy GEGL which evolved into a video compositing end editing application also had a by product of a versatile proof of concept XML based project description [1]. Disregarding the temporal aspects of it, it is a structure that allows for layer groups, effect layers and cloned layers.

I attempted to condense it down somewhat and remove some of the mistakes in the initial implementation and tentativly called that XML structure XCF2[2].

One of the things that would remain for making this kind of format a standard is deciding upon baseline features to be implemented, and a baseline set of operations that need to be supported PNG, SVG, JPG, ICC and EXR might seem like some of the binary formats that are referenced by the catalog.

1: http://pippin.gimp.org/oxide/ 2: http://pippin.gimp.org/xcf2/

/Øyvind K. --
«The future is already here. It's just not very evenly distributed» -- William Gibson http://pippin.gimp.org/ http://ffii.org/

Boudewijn Rempt
2006-03-03 11:15:37 UTC (about 18 years ago)

Archive based project storage with XML catalog

On Friday 03 March 2006 00:07, Øyvind Kolås wrote:

My toy GEGL which evolved into a video compositing end editing application also had a by product of a versatile proof of concept XML based project description [1]. Disregarding the temporal aspects of it, it is a structure that allows for layer groups, effect layers and cloned layers.

I attempted to condense it down somewhat and remove some of the mistakes in the initial implementation and tentativly called that XML structure XCF2[2].

One of the things that would remain for making this kind of format a standard is deciding upon baseline features to be implemented, and a baseline set of operations that need to be supported PNG, SVG, JPG, ICC and EXR might seem like some of the binary formats that are referenced by the catalog.

I'm not sure about jpeg, and a more flexible binary raster format would be needed, too, to support the colormodels png cannot support. And we'd need to have an authoritative list of composite ops and all that kind of thing.