otherwise, you could write your plug-in in Python instead of scheme, and parse these files in 15-20 lines of code. On 26 September 2013 11:48, Kevin Cozens <kevin@xxxxxxxxx> wrote: > On 13-09-25 05:21 AM, Alessandro Francesconi wrote: >> >> I’m developing a plugin that must read the contents of a GIMP “curves” >> file > > [snip] >> >> # GIMP curves tool settings >> >> >> (time 0) >> (channel value) >> (curve >> (curve-type smooth) >> (n-points 17) >> (points 34 0.000000 0.000000 -1.000000 -1.000000 [other X Y >> points...]) >> (n-samples 256) >> (samples 256 0.000000 0.012218 [other samples...]) >> >> ) > > > Hm... interesting. Someone chose to save the settings in a format that looks > a bit like Scheme code. Unfortunately it isn't Scheme-like enough that you > could use the "load" function in a Script-Fu script to load the curve > settings via a script and use the contents of the file. > > The Procedure browser doesn't list any calls for saving or loading curves. > If others thing it would be a worthwhile addition to the API an enhancement > request could be find in bugzilla. > > -- > Cheers! > > Kevin. > > http://www.ve3syb.ca/ |"Nerds make the shiny things that distract > Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're > | powerful!" > #include <disclaimer/favourite> | --Chris Hardwick > > _______________________________________________ > gimp-developer-list mailing list > List address: gimp-developer-list@xxxxxxxxx > List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list