A file format to store process flow and original image untouched
Forums ► For GIMP developers (read-only) ► A file format to store process flow and original image untouched
-
wwp
(3 months ago)
-
Alexandre Prokoudine
(3 months ago)
- wwp (3 months ago)
- Bogdan Szczurek (3 months ago)
-
Alexandre Prokoudine
(3 months ago)
Sent: 2012-02-03 19:48:44 UTC (3 months ago)
From: wwp
A file format to store process flow and original image untouched
Hello there!
I wonder if there's such a storage format, that is, or will (or would
eventually) be supported by Gimp?The idea is to get the process flow (modifications done to an image)
stored to disk, allowing to undo/redo even after reopening the Gimp
later, eventually reuse (parts of) the process flow and apply it to
another image, etc.. I don't care if the process flow is stored with the
original file in the same storage unit or separately.Anyway.. some comments?
Regards,
--
wwp
Sent: 2012-02-03 19:57:24 UTC (3 months ago)
From: Alexandre Prokoudine
A file format to store process flow and original image untouched
On Fri, Feb 3, 2012 at 11:48 PM, wwp wrote:
> Hello there!
>
> I wonder if there's such a storage format, that is, or will (or would
> eventually) be supported by Gimp?
>
> The idea is to get the process flow (modifications done to an image)
> stored to disk, allowing to undo/redo even after reopening the Gimp
> later, eventually reuse (parts of) the process flow and apply it to
> another image, etc.. I don't care if the process flow is stored with the
> original file in the same storage unit or separately.
>
> Anyway.. some comments?Hi,
It's certainly doable. There is some free software like Ardour and
darktable that allows undo/redo across sessions.We haven't really discussed XCF2 much, so I think it would be fair to
say that this is an open question. At some point we need to sit down
and write a functional spec.Alexandre Prokoudine
http://libregraphicsworld.org
Sent: 2012-02-03 20:04:46 UTC (3 months ago)
From: wwp
A file format to store process flow and original image untouched
Hello Alexandre,
On Fri, 3 Feb 2012 23:57:24 +0400 Alexandre Prokoudine wrote:
> On Fri, Feb 3, 2012 at 11:48 PM, wwp wrote:
> > Hello there!
> >
> > I wonder if there's such a storage format, that is, or will (or would
> > eventually) be supported by Gimp?
> >
> > The idea is to get the process flow (modifications done to an image)
> > stored to disk, allowing to undo/redo even after reopening the Gimp
> > later, eventually reuse (parts of) the process flow and apply it to
> > another image, etc.. I don't care if the process flow is stored with the
> > original file in the same storage unit or separately.
> >
> > Anyway.. some comments?
>
> Hi,
>
> It's certainly doable. There is some free software like Ardour and
> darktable that allows undo/redo across sessions.
>
> We haven't really discussed XCF2 much, so I think it would be fair to
> say that this is an open question. At some point we need to sit down
> and write a functional spec.:-)
I presume it's not the first time such topic is raised here. I'm glad
to see that it's an open question, I look forward to see further
discussions!Regards,
--
wwp
Sent: 2012-02-05 00:11:13 UTC (3 months ago)
From: Bogdan Szczurek
A file format to store process flow and original image untouched
> I wonder if there's such a storage format, that is, or will (or
> would eventually) be supported by Gimp?
>
> The idea is to get the process flow (modifications done to an image)
> stored to disk, allowing to undo/redo even after reopening the Gimp
> later, eventually reuse (parts of) the process flow and apply it to
> another image, etc.. I don't care if the process flow is stored with
> the original file in the same storage unit or separately.
>
> Anyway.. some comments?It smells a bit like node editing. It (kind of) showed up recently:
>> I can envision a work-space where you don't really have a layer
>> toolbar open, but a node editor (with backdrop/main image if you
>> need it) which you can scale/re-position, and do all your GEGL
>> operations and magic with nodes, and be back to your main
>> image/paint/edit window with the click of a shortcut.
>
> I'd take it a bit futher: most frequently used node sequences grouped
> together in another nodes, to save, reuse and share with others.Is it close enough to what is on your mind? I hope so, because I love
that idea :).My best!
thebodzio





819 @ Twitter