Re: [Gimp-developer] rectangle select tool specification
On 8/11/06, Kevin Cozens <[EMAIL PROTECTED]> wrote: One feature I miss about the current crop tool is something I'm used to fromthe 2.2 GIMP. I have a habit of using the selection tool to mark a regionthen, when I pick the crop tool, use the "From Selection" option to set the crop limits based on the currently active selection.I suppose I could get used to not having this option in the tool box (or amenu item to do the same thing) but it would be a nice feature to have back. Doesn't this essentially do this for you? I may not fully understand what you are attempting, but you can click inside the current selection, adjust selection/crop then do a Image->Crop to crop the image "from the selection". you click insidean existing selection, then a new, modifiable rectangular selection is created, whose bounds are just large enough to completely enclose theprevious selection.-- Tim Jedlicka, [EMAIL PROTECTED], http://www.galifree.com ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp Perspective Clone Tool
On 8/11/06, Pedro Alonso <[EMAIL PROTECTED]> wrote: The use a keyboard interface is also a good idea, but still to be done.. :)About to see the mouse pointer while setting the perspective plane..currently the cursors are used in the same way as in perspective tool, They aren't! I can see my mouse cursor in the perspective tool!Perhaps my cursor preferences would help you to notice this.. I think i have the cursor set to fancy rendering mode, and to only show the crosshairs. I think that disable linear interpolation would do the tool unusable,here you can see some examples: http://pedroalonso.es/soc/persp.pnghttp://pedroalonso.es/soc/persp2.pngThat's expected and desired behaviour. As I said, subsampling and interpolation have the same problem for me, they add colors; I know that many people don't care about incidentally adding colors, but having direct control over the colors is important for what I do. The rough edges show me where I should touch up manually because the computer can't decide well (these same areas need touchup regardless of whether interpolation is used or not; interpolation reduces definition, no-interpolation reduces smoothness.) If I am forced to use interpolation with a tool, I must adjust colors after each usage of it. Mostly this is unrewarding and tedious; I usually get better results quicker by manual cleanup. And similar with interpolation:http://pedroalonso.es/soc/persp_antialias.pnghttp://pedroalonso.es/soc/persp_antialias2.png http://pedroalonso.es/soc/persp_antialias3.png Can you provide some images where interpolation doesn't works fine? soif this option is needed I can add it to the UISure, when I get my stuff migrated from my old HD completely. Later today, perhaps (depending on how much recompilation is needed) Actually... For your tool to work similarly to the clone tool and perspective tool, I just realized it MUST be able to disable interpolation. Otherwise it doesn't work on INDEXED images (have you tried it on an indexed image yet?) Btw, I have added the same options for paint that are used in clone tool, and have moved the radio buttons where you choose if you aresetting the perspective plane or cloning to the top of the options UI.Good, I'll check that out at the same time. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How to make a PyGimp plugin rerunnable?
On 8/11/06, Seth Burgess <[EMAIL PROTECTED]> wrote: I think the better question is why is it runnable at all? The install_procedure call has an argument of '' for image types it can work on; since you're under the , this should be dynamically changed based upon the characteristics of the image under it. Try using a type of '*' instead, or RGB* if you want to be more specific, and see if that helps. Yes, that was exactly what's needed.Looks like '' means 'image is irrelevant' while '*' means 'all'.Kevin: Nope; read more carefully. it did show up, it just wasn't rerunnable ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] on moving toward a 2.4 release
Date: Fri, 11 Aug 2006 09:09:44 -0700 From: "William Skaggs" <[EMAIL PROTECTED]> GIMP 2.0 was released on March 23, 2004, and then GIMP 2.2 on December 19, 2004. This was a 9 month release cycle, which is quite reasonable. Howver, it has been over a year and a half since the 2.2 release, and we are still not visibly nearing a 2.4 release. This slow progress is holding up important things, including, especially, GEGL integration. What can be done? Compared with us (Gutenprint), that's still positively speedy. GIMP 2.2 is a great application, albeit with some serious limitations (no 16-bit support, etc.). I'd personally prefer to see you folks take more time -- even quite a bit more time -- to get it right rather than try to rush a release. Keep doing 2.2-based releases with incremental functionality while working on a next generation release that will really improve matters. I was hoping that we'd be able to do our followon to Gimp-Print 4.2 within 12-18 months, but it didn't work out that way -- it was more like 4.5 years between Gimp-Print 4.2 and Gutenprint 5.0. There was a lot of churn along the way, but we rearchitected a lot of the internals to come up with a really general option system and a fully orthogonal 16-bit internal architecture (i. e. all of the input types we accept are capable of both 8 and 16 bits). Doing that design -- along with beating the color architecture into shape -- simply took a lot of time. If GEGL integration really is a hard problem, it's going to come out a lot better if you take the time to do it right rather than rushing it. I'd like to see a 16-bit GIMP as much as anyone -- it's a critical part of a RAW-based workflow, and it's needed for HDR imaging, which is something I'd really like to try -- but it's going to be a lot better if it's done right. -- Robert Krawitz <[EMAIL PROTECTED]> Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2 Member of the League for Programming Freedom -- mail [EMAIL PROTECTED] Project lead for Gutenprint --http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] rectangle select tool specification
Sven Neumann wrote: I think it would be sufficient if people could enter a width and a height in order to define the aspect ratio. That's how the old tool used to work. Perhaps add portrait and landscape buttons to it, like we have in the New Image dialog so that people can easily flip the aspect ratio. That sounds like the simplest approach. I don't find the value with all the decimal places after it useful. After entering width/height to set the ratio you would just click the chain icon beside width/height so a change to one of the values adjusts the other accordingly and maintains the desired aspect ratio. One feature I miss about the current crop tool is something I'm used to from the 2.2 GIMP. I have a habit of using the selection tool to mark a region then, when I pick the crop tool, use the "From Selection" option to set the crop limits based on the currently active selection. I suppose I could get used to not having this option in the tool box (or a menu item to do the same thing) but it would be a nice feature to have back. -- Cheers! Kevin. http://www.interlog.com/~kcozens/ |"What are we going to do today, Borg?" Owner of Elecraft K2 #2172|"Same thing we always do, Pinkutus: | Try to assimilate the world!" #include| -Pinkutus & the Borg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] How to make a PyGimp plugin rerunnable?
David Gowers wrote: I've written several PyGimp plugins, but when I go to the 'recent filters' menu or try to rerun one, it is disabled. I can run it okay and it produces the expected results, but I can't rerun it. You don't need to do anything in your plug-in. It was a limitation within GIMP that prevented most (all?) of the script-based plug-ins from appearing in the 'recent filters' list. This has been fixed in the current GIMP source. -- Cheers! Kevin. http://www.interlog.com/~kcozens/ |"What are we going to do today, Borg?" Owner of Elecraft K2 #2172|"Same thing we always do, Pinkutus: | Try to assimilate the world!" #include| -Pinkutus & the Borg ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp Perspective Clone Tool
Hi, - When you define the perspective plane, changes the mode to clone paint, and go back to change the perspective plane mode, it doesn't works. Actually, it does work -- you just can't see it. Switch back to clone mode and you'll see the modified plane. BTW, good work on the interface, it's really intuitive. Thanks, I still have to check it.. My comments on the use of a keyboard interface are still valid, though. And being able to see the mouse pointer while setting the perspective plane would also help a lot. The use a keyboard interface is also a good idea, but still to be done.. :) About to see the mouse pointer while setting the perspective plane.. currently the cursors are used in the same way as in perspective tool, so your purpose would also be for that tool.. I don't really find it necessary... My comment about interpolation I still agree with; For some of my test images interpolation was appropriate, others it blurred unacceptably, so I still think the option to disable it should be provided. I think that disable linear interpolation would do the tool unusable, here you can see some examples: http://pedroalonso.es/soc/persp.png http://pedroalonso.es/soc/persp2.png And similar with interpolation: http://pedroalonso.es/soc/persp_antialias.png http://pedroalonso.es/soc/persp_antialias2.png http://pedroalonso.es/soc/persp_antialias3.png Can you provide some images where interpolation doesn't works fine? so if this option is needed I can add it to the UI The initial coordinates of the plane corners should probably be at the corners of the visible area, rather than the corners of the entire image.. I was confused by this initially. Ok, thinking about it.. hehe. Btw, I have added the same options for paint that are used in clone tool, and have moved the radio buttons where you choose if you are setting the perspective plane or cloning to the top of the options UI. kind regards, Pedro ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] on moving toward a 2.4 release
GIMP 2.0 was released on March 23, 2004, and then GIMP 2.2 on December 19, 2004. This was a 9 month release cycle, which is quite reasonable. Howver, it has been over a year and a half since the 2.2 release, and we are still not visibly nearing a 2.4 release. This slow progress is holding up important things, including, especially, GEGL integration. What can be done? The first step is to make a complete list of the remaining critical functionality issues -- the things that must be resolved in order to permit a string freeze. The most reasonable way of making such a list is to use Bugzilla: every critical issue should have a bug report with target milestone set to 2.4, and severity set to "Blocker". Things that will not prevent a string freeze should not be marked as blockers at this time. I would like to suggest that we set a hard deadline (say Sept 1) for identifying critical functionality issues -- that is, if an issue does not have a "Blocker" bug report by then, it will not be considered critical, and will not prevent a string freeze. Once we have a complete list of issues, we can make a concrete plan on how to deal with them, and start moving forward more efficiiently. In any case, something has to be done to blast us out of the current state of near-paralysis. -- Bill __ __ __ __ Sent via the CNPRC Email system at primate.ucdavis.edu ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] How to make a PyGimp plugin rerunnable?
I've written several PyGimp plugins, but when I go to the 'recent
filters' menu or try to rerun one, it is disabled. I can run it okay
and it produces the expected results, but I can't rerun it.
to clarify, I'm using the simple gimpplugin.plugin class (GimpFu is far
too heavyweight and slow for something with no UI needed)
Here's a super-simplified plugin just to demonstrate this.
How do I get it to be rerunnable?
(pasted here as well as attached, in case the attachment is filtered out by the mailing list software.)
#!/usr/bin/python
import gimp,gimpplugin
from gimpfu import PLUGIN, PF_INT, PF_IMAGE, PF_DRAWABLE, PDB_SUCCESS
pdb = gimp.pdb
import os
class Simple(gimpplugin.plugin):
def query(self):
d = ''
gimp.install_procedure('plug_in_simple',
d,d,d,d,d,'/File/Simple_Test', '',PLUGIN, [(
PF_INT, 'run_mode', "run mode"),(PF_IMAGE, 'image', 'Image'), (PF_DRAWABLE, 'drawable', 'Drawable')]
, [])
def plug_in_simple(self, run_mode, image, drawable):
return # returning
PDB_SUCCESS doesn't help, nor does returning None (as gimpfu.py does)
def start(self):
gimpplugin.plugin.start(self)
if __name__ == '__main__':
Simple().start()
#!/usr/bin/python
import gimp,gimpplugin
from gimpfu import PLUGIN, PF_INT, PF_IMAGE, PF_DRAWABLE, PDB_SUCCESS
pdb = gimp.pdb
import os
class Simple(gimpplugin.plugin):
def query(self):
d = ''
gimp.install_procedure('plug_in_simple', d,d,d,d,d,'/File/Simple_Test', '',PLUGIN, [(PF_INT, 'run_mode', "run mode"),(PF_IMAGE, 'image', 'Image'), (PF_DRAWABLE, 'drawable', 'Drawable')], [])
def plug_in_simple(self, run_mode, image, drawable):
return # returning PDB_SUCCESS doesn't help, nor does returning None (as gimpfu.py does)
def start(self):
gimpplugin.plugin.start(self)
if __name__ == '__main__':
Simple().start()___
Gimp-developer mailing list
Gimp-developer@lists.XCF.Berkeley.EDU
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp Perspective Clone Tool
On 8/11/06, Pedro Alonso <[EMAIL PROTECTED]> wrote: Hi,By other way some things in the tool that have to be fixed are: - When you define the perspective plane, changes the mode to clonepaint, and go back to change the perspective plane mode, it doesn't works. Actually, it does work -- you just can't see it. Switch back to clone mode and you'll see the modified plane. BTW, good work on the interface, it's really intuitive. My comments on the use of a keyboard interface are still valid, though. And being able to see the mouse pointer while setting the perspective plane would also help a lot. My comment about interpolation I still agree with; For some of my test images interpolation was appropriate, others it blurred unacceptably, so I still think the option to disable it should be provided. The initial coordinates of the plane corners should probably be at the corners of the visible area, rather than the corners of the entire image.. I was confused by this initially. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
