Re: Call for plugin maintainance / gflare
I ported Gflare to GIMP 1.1.x with additional help of Daniel Egger. Currently there is only one bug I know: When clicking on edit you get a warning message. I couldn't find the reason why. Please do not remove this plugin from GIMP but help to fix this small problem. Martin
Re: Call for plugin maintainance
On 4 Jan, Sven Neumann wrote: on our way from 1.0 to 1.2 we included a few plug-ins that were considered not to be stable enough to be included with a stable release. This was done in the hope that the inclusion into the 1.1 developement tree would encourage people to work on those plug-ins so that they would become stable enough to be released with 1.2. Hm, there are two thing that are really annoying me: -megawidget -libgck libgtk, libgdk and libgimp should provide all methods which are necessary to build plug-ins. If they do (and I think they do) then there's no reason for existance of these kludges and they should be removed. If they don't we should integrate the necessary functionality into libgimp and thus provide a straightforward and common way to build plug-ins... Yosh: Will these changes have any chance to get into the tree soon if I'm providing the necessary patches? -- Servus, Daniel
Call for plugin maintainance
Hi, on our way from 1.0 to 1.2 we included a few plug-ins that were considered not to be stable enough to be included with a stable release. This was done in the hope that the inclusion into the 1.1 developement tree would encourage people to work on those plug-ins so that they would become stable enough to be released with 1.2. IMO the time has come to doublecheck what plug-ins do fulfill our needs. We have a lot of unmaintained plug-ins in the distribution. Most of them are however quite small, so fixing a bug or doing small changes (like adding gettext support for example) is not too difficult. However there are a few quite large plug-ins (partially written with obscure coding schemes) in our distribution. Some of them are actively developed and maintained by their authors. But unfortunately we have some obviously abandoned projects in our tree. My proposal (and I don't think that anyone can really object against it, since it is the only reasonable way to go) is that we search maintainers for those plug-ins and if we don't find someone feeling responsible we move the plug-in out of the stable tree as soon as a bug is found. I'm not yet sure how this should be organized. I will try to build a complete list of all plug-ins with some information like number of files, codesize, original author, current maintainer and post it here later. Hopefully some people will volunteer to take responsibilities for the abandoned projects. I propose that this list gets included with the distribution so that people know who to contact. Salut, Sven PS: Before I come back with the proposed list, here are some of the plug-ins that I know are broken but too big to fix easily: FractalExplorer GFlare GFig (should at least be cleaned up, the code is one 320k file) libgck (we should get rid of this one or at least rename it) Lighting (has some bugs/disabled features in the preview code)
Re: Call for plugin maintainance
Sven Neumann wrote: [snip sensible idea] libgck (we should get rid of this one or at least rename it) Lighting (has some bugs/disabled features in the preview code) delurk These two are "mine". I have been unable to keep them up to date the last year due to graduating and getting lost in the demands of the Real World (tm). During this year I've gotten two or three mails about the Lighting plug-in, mostly concerning the broken zooming - which should not be too difficult to fix. None about crashes. I would be grateful if those who do find (fatal) bugs drop me a mail about it, I don't have the time at the moment to actively search for bug reports. GCK is AFAIK only used in "my" plug-ins (lic, mapobject, lighting) - I will rewrite them to "pure" G* as soon as I find the time. If someone feels like more actively maintaining the mentioned plug-ins, feel free (and let me know) - I may still do some work on them from time to time, but I can't guarantee it. Best regards, Tom /delurk
Re: Call for plugin maintainance
I wrote: [snip] - which should not be too difficult to fix. None about crashes. Of course, this turns out to be a blatant lie. For the record; I did, in fact, get one such mail - the issue was resolved though. So there. My conscience is now clean. ;) Tom
