The GIMP codebase rigorously separates the UI from the image-manipulation engine, so there is a lot of it you could in principle use. The engine relies on glib and glib-object, but only the UI parts make use of gdk and gtk.

Bill

On Mon, Jun 17, 2013 at 8:14 AM, Alberto Mardegan < mardy@users.sourceforge.net> wrote:

Hi all,
a parallel-universe question: if I were to make a gimp-like application (just somewhat simpler and more limited) with a different UI and toolkit (say, QML), are there some parts of the GIMP codebase that would be useful to me, or would I be better forget about it and start with just using GEGL?

I see that the GIMP codebase consists of many different libs, but I don't have a clear picture of what they do and how much they depend on Gtk.

Ideally, I'd like to be able to re-use the gimp plugins, or at least make porting quite easy.

(Not that I really plan to work on this anytime soon, but if I'll ever be very bored, I might consider doing this as well :-) )

Ciao, Alberto
______________________________**_________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/**mailman/listinfo/gimp-** developer-list

On Mon, Jun 17, 2013 at 7:14 PM, Alberto Mardegan wrote:

Hi all,
a parallel-universe question: if I were to make a gimp-like application (just somewhat simpler and more limited) with a different UI and toolkit (say, QML), are there some parts of the GIMP codebase that would be useful to me, or would I be better forget about it and start with just using GEGL?

I see that the GIMP codebase consists of many different libs, but I don't have a clear picture of what they do and how much they depend on Gtk.

Just use GEGL and https://git.gnome.org/browse/gegl-qt

Alexandre Prokoudine http://libregraphicsworld.org

On 17 June 2013 17:14, Alberto Mardegan wrote:

Hi all,
a parallel-universe question: if I were to make a gimp-like application (just somewhat simpler and more limited) with a different UI and toolkit (say, QML), are there some parts of the GIMP codebase that would be useful to me, or would I be better forget about it and start with just using GEGL?

I see that the GIMP codebase consists of many different libs, but I don't have a clear picture of what they do and how much they depend on Gtk.

Ideally, I'd like to be able to re-use the gimp plugins, or at least make porting quite easy.

The file-loaders in GIMP may be of value, to be able to support many different file formats.
Using libgimp to allow GIMP plugins to work without porting could also have significant value.

Apart from those, GEGL + Qt + gegl-qt should get you a long way.

Jon Nordby - www.jonnor.com

On Mon, 2013-06-17 at 19:14 +0400, Alberto Mardegan wrote:

Hi all,
a parallel-universe question: if I were to make a gimp-like application (just somewhat simpler and more limited) with a different UI and toolkit (say, QML), are there some parts of the GIMP codebase that would be useful to me, or would I be better forget about it and start with just using GEGL?

Probably today I'd use JavaScript and make it a Web application. By the time I'd got something working (I don't go fast) computers would be powerful enough to run it.

And yes, use gegl on the back end.

Liam

Liam Quin - XML Activity Lead, W3C, http://www.w3.org/People/Quin/
Pictures from old books: http://fromoldbooks.org/
Ankh: irc.sorcery.net irc.gnome.org freenode/#xml