Re: [Gimp-developer] 16bit channels, doh
On 10/31/05, Brannon King <[EMAIL PROTECTED]> wrote: > So I was told to see the GEGL info. > > That website (gegl.org) drastically needs a FAQ. > Perhaps someone can answer these questions for me: > > 1. Is GEGL made to replace a certain core piece of > GIMP or is it made to reroute data somehow? > 2. Why is it not part of the GIMP core currently? > 3. Is it activelly being worked on? Is its mailing > list still used? > 4. It appears to just be an API. Why would using this > be better than changing the current GIMP core to > support 16bit channels directly? Or are we planning to > do just that and just use the GEGL API data structures > and constructs? > 5. How close is the GEGL code to usable? > 6. Will it even work with the current GIMP codebase? If memory serves me right, 8-bit support is pretty mostly hard-coded (or something akin to that) in the current GIMP base, unfortunately. Past talk of adding 16-bit support has sounded as though it requires a major revamping of even core underlying systems that comprise GIMP (sounds like a re-write, almost, even). GEGL (Generic Graphical Library) apparently has something to do with the new-fangled underlying framework for such a project. But I have no idea on the subject, I'm just trying to recall what others have said on this list from memory. > 7. Has anyone worked on a merge plan for combining > GEGL work with the current GIMP codebase? I believe it's planned for some future release somewhere, but has been continually put off due to a lack of manpower. Or something of that sort. That said, I'm myself wondering whether a 16-bit capable gimp requires a fork, and if so, how much support that fork would get. Should you go forward with this (and I hope you do, as many have been asking for this), then I do wish you good luck, and hope that it comes out quite well. Because I haven't been following development long enough (I'm afraid), someone else probably has a lot of details to add that I may have missed. -- ~Mike C - Just my two cents - No man is an island, and no man is unable. ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 16bit channels, doh
So I was told to see the GEGL info. That website (gegl.org) drastically needs a FAQ. Perhaps someone can answer these questions for me: 1. Is GEGL made to replace a certain core piece of GIMP or is it made to reroute data somehow? 2. Why is it not part of the GIMP core currently? 3. Is it activelly being worked on? Is its mailing list still used? 4. It appears to just be an API. Why would using this be better than changing the current GIMP core to support 16bit channels directly? Or are we planning to do just that and just use the GEGL API data structures and constructs? 5. How close is the GEGL code to usable? 6. Will it even work with the current GIMP codebase? 7. Has anyone worked on a merge plan for combining GEGL work with the current GIMP codebase? ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 16bit channels, doh
See http://www.gegl.org/ On Monday 31 October 2005 12:42 pm, Brannon King wrote: > It was my plan to write some beautiful DFT and Wavelet > filters for GIMP, as I've done a fair amount of that > for work lately. Then, to my great dismay, I realized > today that there is no support for 12 or 16 bit > channels. Alas, I don't think it's possible without > that feature. I have some time that I could use to > code 16bit channel support if someone could give me > detailed instructions on the matter. I assume it's a > fairly in-depth project, but I'm sure there is a fair > number of requests for the feature as well. > ___ > Gimp-developer mailing list > Gimp-developer@lists.xcf.berkeley.edu > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] 16bit channels, doh
It was my plan to write some beautiful DFT and Wavelet filters for GIMP, as I've done a fair amount of that for work lately. Then, to my great dismay, I realized today that there is no support for 12 or 16 bit channels. Alas, I don't think it's possible without that feature. I have some time that I could use to code 16bit channel support if someone could give me detailed instructions on the matter. I assume it's a fairly in-depth project, but I'm sure there is a fair number of requests for the feature as well. ___ Gimp-developer mailing list Gimp-developer@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Gimp 2.2 Almost running
I have /etc/fonts/fonts.conf loading without error or warning (see below for content) and now I get ... ./gimp-2.2 Bus error a grey window (with a darker gray bar at the bottom) loads immediatly after ./gimp-2.2 for about a 14 count, then the Bus error appears. /etc/fonts/fonts.conf ... /usr/openwin/share/fonts /usr/openwin/lib/X11/fonts /usr/local/GIMP/share/gimp/2.0/fonts mono monospace mono monospace sans ~/.fonts.conf conf.d local.conf Times Times New Roman serif Helvetica Arial sans Courier Courier New monospace serif Times New Roman sans Arial monospace Andale Mono
[Gimp-developer]
Yavala writes:
> Can someone help me with the simple plug-in (hello message
> box)http://developer.gimp.org/writing-a-plug-in/1/index.html?
Well, the most obvious error is that there is no initial '#' character
on the line where you try to include libgimp/gimp.h. (Have you never
programmed in C before?) It should look like this:
#include "libgimp/gimp.h"
You also need to have the PLUG_IN_INFO array and MAIN(). Add the
following to the bottom of the source file:
GimpPlugInInfo PLUG_IN_INFO =
{
NULL, /* init_proc */
NULL, /* quit_proc */
query, /* query_proc */
run, /* run_proc */
};
MAIN ()
The menu path to the plug-in that is passed to
gimp_install_procedure() needs to start with . Change it as
follows:
gimp_install_procedure (
"plug_in_hello",
"Hello, world!",
"Displays \"Hello, world!\" in a dialog",
"David Neary",
"Copyright David Neary",
"2004",
"/Filters/Misc/Hello world...",
"RGB*, GRAY*",
GIMP_PLUGIN,
G_N_ELEMENTS (args), 0,
args, NULL);
}
With these changes your plug-in compiles and works fine with GIMP 2.2.
--tml
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
