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@xxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxx > List membership: https://mail.gnome.org/**mailman/listinfo/gimp-** > developer-list<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
