---------- Forwarded message ----------
From: GIMP <bugzilla@xxxxxxxxx>Date: Thu, Dec 24, 2009 at 3:04 PM
Subject: [Bug 605366] OpenRaster support
To: jononor@xxxxxxxxx
https://bugzilla.gnome.org/show_bug.cgi?id=605366
GIMP | General | unspecified
Martin Nordholts <enselic> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |enselic@xxxxxxxxx
Target Milestone|--- |2.10
Ever Confirmed|0 |1
--- Comment #1 from Martin Nordholts <enselic@xxxxxxxxx> 2009-12-24 14:03:58 UTC ---
The best way to get OpenRaster into GIMP is better discussed on the
gimp-developer mailing list, but I think GIMP 2.10/3.0 will be a good time to
seriously look into this.
-----------------
Picking up this right now. As stated in the report, there is a Python input handler plug-in (written by me) available that provides OpenRaster support. Are you be interested in shipping this for 2.8? What would it take?
Obviously that solution is not good enough in the long term. So what would be the best approach for a long term solution? Right now, I see two viable alternatives:
1) Making a separate library thats suitable for use from C that handles the low-level/OpenRaster specific stuff. MyPaint and other apps could possibly use this as well.
2) Implement support directly in GIMP. Possibly using GEGL(?)
Regards Jon Nordby - www.jonnor.com
_______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
