Eric Pierce wrote:
Thanks both of you for the links.
Damn... I'm intimidated to say the least. Looks like I've got some
reading ahead of me.
Do not be.
You don't actually HAVE to go through it all to code for the GIMP.
Just browse the code...when you come accorss something you can figure
out
Thanks both of you for the links.
Damn... I'm intimidated to say the least. Looks like I've got some
reading ahead of me.
Ta ta,
Eric Pierce
> Eric Pierce wrote:
>> Forgive my naivety, but what would be a good way to plunge into some
>> Gimp
>> code and maybe even help out someday?
>
> We need
Eric Pierce wrote:
> Forgive my naivety, but what would be a good way to plunge into some Gimp
> code and maybe even help out someday?
We need lots of people, for everything from bug fixing to plug-in
maintenance, and core development. Plug-ins are smaller, so
getting into those is somewhat easier
Hi,
"Eric Pierce" <[EMAIL PROTECTED]> writes:
> Forgive my naivety, but what would be a good way to plunge into some
> Gimp code and maybe even help out someday?
Subscribe to the gimp-developers mailing list, read the code, consider
to look into the docs at http://developer.gimp.org/api/1.3/. Ma
Forgive my naivety, but what would be a good way to plunge into some Gimp
code and maybe even help out someday?
I currently do web development (PHP, JavaScript, ColdFusion) and I've
mucked a little with C/C++ and I even did some Assembler programming on
the (don't laugh) Apple ][+ years back.
Any
