Re: [Gimp-developer] app icon update proposal
Hi, Jakub Steiner <[EMAIL PROTECTED]> writes: > I have refreshed the look of GIMP's mascot as an app icon and propose > this to be included upstream. The icon follows the Tango Style > Guidelines [1] (to a great extent) but is mostly based on the original > shape and colors originally crafted by Tuomas Kuosmanen [2]. The problem with desktop files is that, as far as I know one can only specify a single application icon. So if we can agree that we want to use these icons, I would replace that the 48x48 icon in the gimp source tree with the 48x48 icon you proposed. We should probably also replace the icons we use as window icons, but we would need them at 16, 32, 48 and 64 pixels then. Do we also want to replace the question / warning / error icons with the ones from http://jimmac.musichall.cz/i.php?i=Tango-GIMP ? That would make sense if GTK+ would also adapt the Tango style for their icons. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: [Gimp-user] `Bucket fill' ..
Hi, "Nathan Summers" <[EMAIL PROTECTED]> writes: > Maybe I'm not understanding what's wanted here, but I get the > impression that they're talking about a tool that you could use to > e.g. change the color of a shirt someone is wearing without loosing > the lighting and shading. That would be a pretty cool tool to have, > and I can imagine a decent algorithm for doing it, but I can't think > of a reasonable way to do it with the existing tools. Select the shirt, then use the Colorize tool on the selection? > Again, yes, a useful tool. But I think that before we go about > making more tools, we finally implement pluggable tools. To avoid > the problems we had last time, I suggest that we come up with a sane > tool API, implement it in the core, port several tools over to it, > and then after it's fairly stable worry about finding a way to do > things out-of-process. Coming up with a sane tool API is the hard part. The current core API is far from being sane. Sven ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: [Gimp-user] `Bucket fill' ..
On 3/27/06, Sven Neumann <[EMAIL PROTECTED]> wrote: > Hi, > > "Gerald Friedland" <[EMAIL PROTECTED]> writes: > > > True. As long as you have got an appropiate selection too, you could > > select the object, fill it, and you are done. A "natural" bucket fill > > would just be a short cut to this process. > > Do we really need the overhead in code and complexity to achieve > something that can be easily done in two steps? I think that using the > selection tools followed by a fill is the natural way to achieve the > desired effect and it is also a lot more flexible than a dedicated > tool. Maybe I'm not understanding what's wanted here, but I get the impression that they're talking about a tool that you could use to e.g. change the color of a shirt someone is wearing without loosing the lighting and shading. That would be a pretty cool tool to have, and I can imagine a decent algorithm for doing it, but I can't think of a reasonable way to do it with the existing tools. > If someone wants to put effort into a specialised tool, maybe it could > be a red-eye-removal tool because that is really an often requested > feature and it is not easily achievable using a combination of the > existing tools. Again, yes, a useful tool. But I think that before we go about making more tools, we finally implement pluggable tools. To avoid the problems we had last time, I suggest that we come up with a sane tool API, implement it in the core, port several tools over to it, and then after it's fairly stable worry about finding a way to do things out-of-process. Nathan ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
