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

developer with spare time.

This discussion is connected to the gimp-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.

5 of 5 messages available
Toggle history

Please log in to manage your subscriptions.

developer with spare time. andy gill 11 Jan 16:19
  developer with spare time. " 11 Jan 17:13
   developer with spare time. andy gill 11 Jan 17:47
    developer with spare time. " 11 Jan 18:01
     developer with spare time. " 11 Jan 18:04
andy gill
2011-01-11 16:19:02 UTC (almost 14 years ago)

developer with spare time.

Hello, I'm a coder with some spare time, wondering how to spend it. Are there any jobs that could be usefully picked up by someone who isn't one of the core developers?

"
2011-01-11 17:13:33 UTC (almost 14 years ago)

developer with spare time.

On Tue, Jan 11, 2011 at 4:19 PM, andy gill wrote:

Hello, I'm a coder with some spare time, wondering how to spend it. Are there any jobs that could be usefully picked up by someone who isn't one of the core developers?

One thing that will prove beneficial in the future, is the porting more of the plug-ins GIMP ships with by default to also be available GEGL ops. (thus preparing for the time when GIMP is internally using GeglBuffers and having >8bpc ways of processing is more important.

Looking at various files in common/ and other subdirectories of http://git.gnome.org/browse/gegl/tree/operations/ should provide a guide to how such ops can be implemented.

Such contributions would be completely self-contained and thus not need any changes to infrastructure.

Such ops would at first only be available through the GEGL tool with automatically constructed property UIs. I expect at some point that there will also be seperatly loadable plug-ins providing custom UIs for specific GEGL ops. (This is something I believe might belong in GIMP not GEGL; or perhaps even in a gegl-gtk-ui convenience library).

/Øyvind K. --
http://pippin.gimp.org/

Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
andy gill
2011-01-11 17:47:30 UTC (almost 14 years ago)

developer with spare time.

That certainly looks like something I could help with. Is there a priority list of missing operations, or is it more a case of just going through the gimp filters one by one? Is it the final intention that all gimp filters will be implemented by gegl one day?

Andy.

On 11 January 2011 17:13, Øyvind Kolås wrote:

On Tue, Jan 11, 2011 at 4:19 PM, andy gill wrote:

Hello, I'm a coder with some spare time, wondering how to spend it. Are there any jobs that could be usefully picked up by someone who isn't

one

of the core developers?

One thing that will prove beneficial in the future, is the porting more of the plug-ins GIMP ships with by default to also be available GEGL ops. (thus preparing for the time when GIMP is internally using GeglBuffers and having >8bpc ways of processing is more important.

Looking at various files in common/ and other subdirectories of http://git.gnome.org/browse/gegl/tree/operations/ should provide a guide to how such ops can be implemented.

Such contributions would be completely self-contained and thus not need any changes to infrastructure.

Such ops would at first only be available through the GEGL tool with automatically constructed property UIs. I expect at some point that there will also be seperatly loadable plug-ins providing custom UIs for specific GEGL ops. (This is something I believe might belong in GIMP not GEGL; or perhaps even in a gegl-gtk-ui convenience library).

/Øyvind K. --
http://pippin.gimp.org/

"
2011-01-11 18:01:13 UTC (almost 14 years ago)

developer with spare time.

On Tue, Jan 11, 2011 at 5:47 PM, andy gill wrote:

That certainly looks like something I could help with. Is there a priority list of missing operations, or is it more a case of just going through the gimp filters one by one? Is it the final intention that all gimp filters will be implemented by gegl one day?

Yes, the expectation is that one day all the code that directly modifies pixel values are GeglOperations, when it comes to core (non-plugin) functionality a lot of this migration has already been done and can be seen in http://git.gnome.org/browse/gimp/tree/app/gegl

/Øyvind Kolås

«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
"
2011-01-11 18:04:48 UTC (almost 14 years ago)

developer with spare time.

On Tue, Jan 11, 2011 Øyvind Kolås wrote:

.... http://git.gnome.org/browse/gegl/tree/operations/ (GEGL plug-in ops) ... http://git.gnome.org/browse/gimp/tree/app/gegl (GEGL ops statically compiled into GIMP)

Note these two ways of creating GeglOperation subclasses lead to almost exactly the same compiled code, the first one uses custom C-preprocessor macros to avoid the boiler plate needed to define GObject subclasses and properties.

/Øyvind K.

«The future is already here. It's just not very evenly distributed»
                                                 -- William Gibson
http://pippin.gimp.org/                            http://ffii.org/
_______________________________________________
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer