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
New plug-in
Hello, I have made a plug-in that does some interesting things, like applying a theme taken from one image and applying it to another, or making an image tilable. More details at http://yoyo.cc.monash.edu.au/~pfh/fixer/ This is my first plug-in (and my first post to this list). Any comments would be appreciated, especially about any GIMP conventions i may have inadvertantly missed. A question about patents. Is putting something on the web enough to prevent someone patenting it, or could someone download my plug-in and then patent the algorithm? regards, ^^, Paul Harrison Email: [EMAIL PROTECTED] Web: http://yoyo.cc.monash.edu.au/~pfh/ grey spiderwebs partition space
Re: New plug-in
A question about patents. Is putting something on the web enough to prevent someone patenting it, or could someone download my plug-in and then patent the algorithm? Your plugin is prior art so patents can not be taken. But web is still a weird place, so you will have to convice lawyers that it is your and since day X. What I would do is to register your plugin (copyright office) or get an official stamp (notary? I hope that is the correct word for the guy who does that). In other words, an official doc that says that since day X your app exists, and is yours. So if anybody tries to patent it he will be unable to get it (prior art) or will get a void patent (due lack of prior art research). I think that the copyright registration is not expensive, and as legal evidence it should be enough. And it will also in the case of somebody not following your license. Anyway, check with a lawyer, IANAL. GSR
Re: New plug-in
On Fri, 7 Jan 2000 23:40:02 +1100 (EST), Paul F Harrison [EMAIL PROTECTED] said: I have made a plug-in that does some interesting things, like applying a theme taken from one image and applying it to another, or making an image tilable. More details at http://yoyo.cc.monash.edu.au/~pfh/fixer/ This is my first plug-in (and my first post to this list). Any comments would be appreciated, especially about any GIMP conventions i may have inadvertantly missed. It's incredibly slow, probably because you did a naive iteration across the image instead of using pixel regions. Doing direct iterations across a gimp image thrashes the system badly and is an evil thing to do. Please rewrite your code to use pixel regions and rerelease. (I'd do it myself but I'm on other tasks ATM.) Kelly
Re: cvs can't create .gimp-1.1
On Fri, Jan 07, 2000 at 06:02:11AM -0800, [EMAIL PROTECTED] wrote: Without a pre-existing .gimp-1.1 directory, gimp cvs will lock up immediately after you issue "gimp" at the command line. strace gimp reports over and over, at the end, that: read(3, "\23\357w\0\27\0\200\1\27\0\200\1"..., 32) = 32 ioctl(3, FIONREAD, [0]) = 0 read(3, 0xbfffef80, 32) = -1 EAGAIN (Resource temporarily This is probably _not_ related to the missing .gimp-1.1 directory. Incidently, gimp asks me to create it (and does so) here. So the error must be somewhere else. Could you provide a full strace listing (to me, possibly bzipped? thanks ;) Also, strace is _very_ unreliable (at least on linux), so the real bug might be not related to the strace output at all. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
