feature requests?
Howdy, Is there a feature request database for Gimp? If not, I would like to request that a bug group for feature requests (preferrably with some level of urgency) be added to the bugtracker on sourceforge. It would be nice to have an exhaustive list of what people wanted and not depend on "institutional knowledge". My request is a "sort color table" option so that I can more easily reduce the color table by hand. -Dean Johnson Tool Hooligan Cluster Admin Tools Jessie Project Silicon Graphics Inc.Eagan,MN (651) 683-5880 "I am Dyslexic of Borg, Your Ass will be Laminated"-- unknown
Re: feature requests?
On Sat, Jan 29, 2000 at 02:28:47PM -0600, Dean Johnson wrote: Howdy, Is there a feature request database for Gimp? Yes, file a bug as usual, but set your (is it urgency? priority? I don't remember, but I'm pretty sleepy right now) to show that it's a feature request/ request for enhancement. This is with the central Gimp bug database, on bugs.gnome.org, I think Gimp News has a good link directly into the system, but I do not know if you can file RFEs through Gimp News. NB No more features for 1.1.x - Right 'em down, file 'em and remind us about it when we're all partied out from releasing 1.2.0. Nick.
Re: feature requests?
On Sat, Jan 29, 2000 at 04:38:52PM -0500, Kelly Lynn Martin wrote: If by "color table" you mean the indexed color palette, that will require core modifications (I believe) because I don't think palettes are exposed to plug-ins well enough to do operations on them. What do you mean by "well enough to do operations on them" ? All the existing plug-ins that work with palettes (INDEXED images would be even more useless than they already are if no plug-ins could work with them) use calls like: palette= gimp_image_get_cmap(image, entries); /* and */ gimp_image_set_cmap(image, palette, entries); That enough? (remember we're talking about = 768 bytes here) Nick.
Re: feature requests?
On Sat, 29 Jan 2000 21:53:47 +, Nick Lamb [EMAIL PROTECTED] said: All the existing plug-ins that work with palettes (INDEXED images would be even more useless than they already are if no plug-ins could work with them) use calls like: I guess it's GIMP palettes that are badly exposed. IIRC, there's no PDB call to create, modify, or destroy a palette. Indexed colormaps are obvously editable or the GIF plugin wouldn't work. :) Kelly
Re: feature requests?
On Sat, Jan 29, 2000 at 09:53:47PM +, Nick Lamb [EMAIL PROTECTED] wrote: What do you mean by "well enough to do operations on them" ? Probably "You cannot read/modify/list/do anything with the colormaps in the gimp." The only thing you can work on is the colormap of some indexed image. But even simple things like dithering to a specific colormap are not possible. If you have ever asked yourself why the "Smooth colour palette"-plug-in outputs an image and not a colormap, than you now know why. I hope somebody will find it critical enough to implement the PDB interface ;) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: feature requests?
On Sun, 30 Jan 2000 00:11:47 +0100, Marc Lehmann [EMAIL PROTECTED] said: If there were a way of adding a prominent notice like "DO NOT USE THIS BUG-TRACKER TO REPORT GIMP BUGS, INSTEAD, GO TO http..."... Have you asked Sourceforge? Kelly
Re: feature requests?
On Sat, Jan 29, 2000 at 07:08:49PM -0500, Kelly Lynn Martin [EMAIL PROTECTED] wrote: If there were a way of adding a prominent notice like "DO NOT USE THIS BUG-TRACKER TO REPORT GIMP BUGS, INSTEAD, GO TO http..."... Have you asked Sourceforge? I would rather have them fixed their %$%$ยง cvs server first, as I cannot check in to htdocs or CVSROOT at the moment, other directories will follow soon ;( But yes, that might be a good idea ;) I also thought about at least a mailinglist "gimp-plug-ins-admin" to contact somebody with admin access. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: feature requests?
On Sun, Jan 30, 2000 at 01:31:52AM +, Nick Lamb [EMAIL PROTECTED] wrote: Well, the mail I replied to (from Kelly I think) talked about indexed palettes or colourmaps or somesuch, and the word indexed to me means the kind applied to INDEXED images. So I explained how to get at them from the PDB, Sure ;) but there's a much EASIER way for the other kind. Gimp palettes are files :) So plug-ins should duplicate the palette file parser, scan all direcrories where gimp looks for palette files to find the palette is looking for, and then restart gimp to take notice of the changed files? You can open, examine, edit and save the Gimp's palette files, I do not Not programmatically. Hey - This might be perfect for a Perl plug-in, since it does text munging and should preferably be written without breaking the feature freeze - no? No. It's just insensible to duplicate code and make it a hassle for developers when the code already exists within the gimp. Especially since there is no way to make gimp _find_ your palette file after you have written it. I hope somebody will find it critical enough to implement the PDB interface ;) We shouldn't add more PDB interfaces to 1.1.x unless they fix a bug That's fine. This just means that palettes cannot be managed via plug-ins, just as was said before. fopen() works here. Nope. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: feature requests?
On Sun, Jan 30, 2000 at 02:38:07AM +0100, Marc Lehmann wrote: So plug-ins should duplicate the palette file parser, scan all direcrories where gimp looks for palette files to find the palette is looking for, and then restart gimp to take notice of the changed files? "duplicate the palette file parser" rather overstates the problem, if you take a look at the file format you'll wonder what all the fuss is about -- it's not even High School Chemistry, let alone Rocket Science The fabled "Swiss Army Chainsaw" ought to make short work of it. The modern Gimp ships with exactly ONE, count them, directory in the palette search path, so for a quick fix (yes, that's what this is, otherwise I wouldn't have proposed using Perl) we can use an existing PDB lookup to guess the correct directory in 1 line of code. Then you open a dialog which says 'Sorry about this old chap, but I'm afraid you'll have to click "Refresh" in the poorly designed Palette Edit dialog, we promise to make this less evil in a future incarnation of the Gimp'. All done. That's fine. This just means that palettes cannot be managed via plug-ins, just as was said before. I happen to think that the above is better than admitting defeat and saying "We can't do that AT ALL". If a user agrees sooner or later they'll do it themselves (canny wee people users). Anyway, I suppose it's about time that I looked closely at what was originally requested, to figure out who I should suggest this Perl hacking exercise to (you will accept it if they write it Marc, right?) Nick.
Re: feature requests?
On Sun, Jan 30, 2000 at 02:10:33AM +, Nick Lamb [EMAIL PROTECTED] wrote: "duplicate the palette file parser" rather overstates the problem, if You picked probably the least important problem :( Then you open a dialog which says 'Sorry about this old chap, but I'm afraid you'll have to click "Refresh" in the poorly designed Palette Edit dialog, we promise to make this less evil in a future incarnation of the Gimp'. All done. Yes, thats not "easy to do", its more like "broken by design". I happen to think that the above is better than admitting defeat and saying "We can't do that AT ALL". We still can't do that from a plug-in, there is no point in arguing about that. hacking exercise to (you will accept it if they write it Marc, right?) With accept you mean "put into the distribution"? I surely have accepted much worse hackery in the past ;- -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: feature requests?
On Sun, 30 Jan 2000 01:31:52 +, Nick Lamb [EMAIL PROTECTED] said: Gimp palettes are files :) Yes, but when you have LOTS of custom palettes, having "Reload" as the only way to get a new palette into the GIMP is NOT pleasant. (I have hundreds of custom palettes and have had, at times, THOUSANDS of custom gradients.) I'm not even sure that the PDB exports the reload option, either. We shouldn't add more PDB interfaces to 1.1.x unless they fix a bug Unexported functionality, IMO, is a bug. Kelly
