RSS/Atom feed Twitter
Site is read-only, email is disabled

Porting GEGL

This discussion is connected to the gegl-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

Porting GEGL scl 09 Apr 22:38
  Porting GEGL Alexandre Prokoudine 10 Apr 07:57
  Porting GEGL Alexandre Prokoudine 15 Apr 10:00
   Porting GEGL scl 16 Apr 17:10
scl
2013-04-09 22:38:13 UTC (over 11 years ago)

Porting GEGL

Hi,

as a foundation for the further GEGL porting work, the LGM and GSOC 2013 I updated the GEGL porting matrix in our developer wiki [1]. Please review.

I think - despite of all the respectable work done - it's no secrets to say that the GEGL port has been a topic for long, is still a show stopper for version 2.10 and all further work and yet there's still a lot to do. Beside others currently 43% of the filters are ported. Don't get me wrong - I'm not blaming anybody. Let's see how we can boost the process.

I think the following could help: - Get rid of filters that don't match to the product vision or are outdated. Priorize the remaining filters. Alexandre wrote a mindstorm article [2] in the wiki and I fully agree with it. The LGM is a good opportunity to discuss it and also we have the mailing lists and IRC. Ask the artists at LGM and in our mailing lists about their needs. - Focus the 2013 GSOC projects on the GEGL port. - Port only a set of core functions and let the other functions do their work through PDB-API calls from a scripting language (Script-Fu or Python), if that can be done easier than writing C code. So the other functions could inherit silently all the GEGL capabilities. - If other open source projects, like Darktable, Digikam, OpenCV, RawTherapee etc., have solutions for our missing filters, why not call their libraries through GEGL in a first step?

Kind regards,

Sven

[1] http://wiki.gimp.org/index.php/Hacking:Porting_filters_to_GEGL [2]
http://wiki.gimp.org/index.php/Mindstorm:Revamping_default_plugins_and_scripts

Alexandre Prokoudine
2013-04-10 07:57:28 UTC (over 11 years ago)

Porting GEGL

On Wed, Apr 10, 2013 at 2:38 AM, scl wrote:

- If other open source projects, like Darktable, Digikam, OpenCV, RawTherapee etc., have solutions for our missing filters, why not call their libraries through GEGL in a first step?

1) They got no libraries (except OpenCV which is a library). 2) I don't really understand what you meant with that call :)

Alexandre Prokoudine http://libregraphicsworld.org

Alexandre Prokoudine
2013-04-15 10:00:28 UTC (over 11 years ago)

Porting GEGL

On Wed, Apr 10, 2013 at 2:38 AM, scl wrote:

Hi,

as a foundation for the further GEGL porting work, the LGM and GSOC 2013 I updated the GEGL porting matrix in our developer wiki [1]. Please review.

Re: "(1) This filter was marked as GEGL ported in the previous version of this document, but the source file could not be found in GEGLs master branch. Is there a confusion with the file loaders/savers in GIMP?"

I don't understand why you were trying to look for source code in GEGL's repository :) Plug-ins don't necessarily have to be implemented as GEGL ops. Yes, it's nice, but not necessary. Rewriting them to use GEGL buffers is sufficient for now. Could you please fix the wiki? :)

Alexandre Prokoudine http://libregraphicsworld.org

scl
2013-04-16 17:10:01 UTC (over 11 years ago)

Porting GEGL

On 15.04.13 12:00 AM Alexandre Prokoudine wrote:

Yes, it's nice, but not necessary. Rewriting them to use GEGL buffers is sufficient for now. Could you please fix the wiki? :)

Thank you for reviewing and claryfing this. The wiki-fix is in progress.

Kind regards,

Sven