Re: New plug-in
Hi there, 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? (I don't have the original mail anymore...) The best thing I can think of is to have a copy of the source code notarized and stored in a safe-deposit box. You could mail it to yourself, but a notarization is probably stronger legally (because the notary can testify). A copyright registration might not be sufficient since you're not required to deposit the full source code for a TX Unpub registration. It would provide evidence of prior art, at least; whether it would be sufficient, I can't say. Ask a patent lawyer. I would go for the "Eternal logfile", run by Lutz Donnerhacke. See http://www.iks-jena.de/mitarb/lutz/logfile/ for more information. (In short, it's a logfile which is secured by several hash functions and these hashes are made public once in a while so everything you write to it cannot be altered later without noticing. So you just submit an MD5 sum of your source to the logfile with a comment stating what it is and whom it belongs to.) HTH! Tino. -- * LINUX - Where do you want to be tomorrow? *
Gimping around in BeOS
Does anybody know of an easy way to get the GIMP working in BeOS?
[gimpwin-users] PNG blank display bug
Matt.Wilkie writes: I'm getting this weird display problem with some PNG images, a sample is attached. Please let me know if you do/don't have similar problems. The PNG apparently claims to have the display (and print) resolution of 0 pixels/inch... Set it with ImageScale ImagePrint Size Display UnitResolution X and Y and the image appears. The PNG plug-in probably should check for this and use some sensible default if the file claims 0 dpi? --tml
Re: [gimpwin-users] PNG blank display bug
Matt.Wilkie writes: I'm getting this weird display problem with some PNG images, a sample is attached. Please let me know if you do/don't have similar problems. The PNG apparently claims to have the display (and print) resolution of 0 pixels/inch... Set it with ImageScale ImagePrint Size Display UnitResolution X and Y and the image appears. The PNG plug-in probably should check for this and use some sensible default if the file claims 0 dpi? I have changed the core so that it does not accept zero resolutions. Additionally I have changed all plug-ins that try to set the resolution to check the value and simply don't set it at all if it is invalid. Gimp will then use the default set up by the user. Salut, Sven
Re: [gimpwin-users] PNG blank display bug
I have changed the core so that it does not accept zero resolutions. Additionally I have changed all plug-ins that try to set the resolution to check the value and simply don't set it at all if it is invalid. Gimp will then use the default set up by the user. Please make sure that XCF loading is not exempt from these checks. (XCF loads seem to bypass core sanity checking sometimes..) Thanks for the tip. It looks like XCF did it right this time and by looking at it I found that we have definitions for GIMP_MIN_RESOLUTION and GIMP_MAX_RESOLUTION. So the core now checks for these bounds. I have again removed the checks from the plug-ins since this only bloats the plug-in code. Salut, Sven Kelly
Re: [gimpwin-users] PNG blank display bug
On Sat, Jan 08, 2000 at 11:16:45AM +0200, Tor Lillqvist wrote: The PNG apparently claims to have the display (and print) resolution of 0 pixels/inch... Set it with ImageScale ImagePrint Size Display UnitResolution X and Y and the image appears. The PNG plug-in probably should check for this and use some sensible default if the file claims 0 dpi? Mmmm. Can someone tell me which app or lib is settings pHYs == 0 ? I think png-implement would like to know about anyone stupid enough to actually do that (it's an optional chunk, so if you don't know what to put in it, why write it at all?) If you have a suitably broken PNG which is non-sensitive then I'd also like a copy to add to my collection of test images. Nick.
Re: Print 3.0.3.1
Experimental release 3.0.3.1 is now on my web site. My printer currently has a partially clogged magenta head that I have not yet been able to clear, so colors don't print true (this is why the "experimental"). Nonetheless, I have been able to make some improvements: 1) Dark midtones should print smoother. 2) Performance improvements. 3) Minor bug fix in PostScript printing, from Salvador Pinto Abreu. 4) Support for softweave for more Epson printers (VERY EXPERIMENTAL -- I cannot test this to any significant degree, although I do have unit tests for the weave code!). Also, some code restructuring to generalize the softweaving, at least within the Epson code. I've received requests for support for the 440/640/740 printers. They don't look too hard (they appear on first reading to be fairly generic printers), but I don't have this equipment available... -- Robert Krawitz [EMAIL PROTECTED] http://www.tiac.net/users/rlk/ Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton
Gimp splash images
Hi: I would like to get all the splash images avaliable. I have some, but not all, from .tar.bz2 files (mainly latest). Could somebody tell me if they have been archived? Where? If something about CVS, please a web or any other way to get inside. Thanks in advance. GSR
timing actions?
Hello, Is there a standard (or recommended) way in GIMP to get timings of various filters and scripts? Looking in scrip-fu, it puts out timing info to the server log, but that is at 1 second granularity, which is insufficent for serious timing. It looks like I can get at a higher resolution timer through Perl, but I would rather get the information from something a little more tightly integrated with GIMP. -Dean Johnson Tool Hooligan Jessie Project Silicon Graphics Inc.Eagan,MN (651) 683-5880 "I am Dyslexic of Borg, Your Ass will be Laminated"-- unknown
