Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems

2003-03-30 Thread Simon Budig
Sven Neumann ([EMAIL PROTECTED]) wrote: > My point is that we should first clean up the internal API and provide > a framework that allows an experienced GIMP developer to create a new > tool without loosing his/her mind. Yesss!! pleze! Bye, Simon -- [EMAIL PROTECTED]

Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems

2003-03-30 Thread Sven Neumann
Hi, Nathan Carl Summers <[EMAIL PROTECTED]> writes: > While we should have a good specification of the "tool api," not thinking > about plugging issues would be counterproductive. Many of the existing > issues are related to the nonextensiblity of the current api. My point is that we should fir

Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems

2003-03-30 Thread Nathan Carl Summers
On 30 Mar 2003, Sven Neumann wrote: > Hi, > > Nathan Carl Summers <[EMAIL PROTECTED]> writes: > > What needs to be done for the next release is a major cleanup of the > tools. I agree. > Part of this cleanup should be a proper documentation on how to > write a GIMP tool. Providing source for a

Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems

2003-03-30 Thread Sven Neumann
Hi, Nathan Carl Summers <[EMAIL PROTECTED]> writes: > The last time I checked, in-process tool plugin loading worked with only > a handful of mild issues to be resolved. I have no doubt that it can be > in perfect working order in less than two weeks. sorry, last time I checked, tools in GIMP w

[Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems

2003-03-28 Thread Nathan Carl Summers
I'm sorry that I haven't been able to do much GIMP participation in the last several months. I don't want to bore everyone here with details of my personal life, so suffice it to say I haven't been able to spend much time hacking or even replying to email. I regret any inconvenience this has caus