Re: [Gimp-developer] Default values for the Fixed: Size entry (WAS: Gimp (current svn) crop tool)

2007-08-21 Thread Martin Nordholts
peter sikking wrote: > Guys, > Hello guiguru, (It was an odd time stamp on your mail. are you back from vacation yet?) The spec asks for ideas for good default values for the Fixed: Size entries. How about having 100x100 as default when there is no pending rectangle and rectangle width x rect

[Gimp-developer] Feature request, - liquid resize

2007-08-21 Thread Thomas Lytje
I am not sure you take feature requests like this, - but try to take a look. It seems quite cool. I don't know enough about image processing (but I am a software engineer) but to me it looks like it wouldn't be to hard to implement. Hopefully there isn't a lot of patens making it impossible See: h

[Gimp-developer] Is it too late to send a l10n patch for GIMP 2.4.0?

2007-08-21 Thread Choi, Ji-Hui
Hi. I'm new in gimp development. few day ago, I checked gimp 2.4 rc1 source, and then I noticed the l10n file for korean was so terrible. it means translation was not apply almostly. so I contacted our tongue translator, and got an answer. "it's for you." :-( BTW, so I fixed, reassigned, etc.. n

Re: [Gimp-developer] Gimp (current svn) crop tool

2007-08-21 Thread peter sikking
Guys, the fixed ratio/width/height/size functionality is optimised for applying that constraint many times over a period of time (all day long). You set it up, then you use it for a while. If you quickly want to set the width/height/size of the bounding rectangle then there are the width and

Re: [Gimp-developer] Gimp (current svn) crop tool

2007-08-21 Thread Liam R E Quin
On Tue, 2007-08-21 at 08:34 +0200, Martin Nordholts wrote: > It seems to me as if you describe Fixed: Size simply as a facility to > lock the current size. That was the case before I started to implement > guiguru's rectangle tools spec [1], but it's not the case anymore, so > your argumentatio

Re: [Gimp-developer] Gimp (current svn) crop tool

2007-08-21 Thread Martin Nordholts
Liam R E Quin wrote: > On Tue, 2007-08-21 at 08:34 +0200, Martin Nordholts wrote: > However, with latest svn it's still frustrating: > (1) open a medium-sized image, e.g. 1000x3000 pixels > (2) press C to choose crop tool, and drag out a rectangle of > (say) several hundred pixels on a side >

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Amit Kumar Saha
Hello Michael, On 8/21/07, Michael J. Hammel <[EMAIL PROTECTED]> wrote: > The trick here isn't creating an extensible plugin. The trick is > defining what "without much hassle on the part of the end-user" really > means. Who's the end user? Joe Artist or Edward Engineer? Sven's > granny or a

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Amit Kumar Saha
Hello Kevin, On 8/21/07, Kevin Cozens <[EMAIL PROTECTED]> wrote: > As Michael mentioned, using a scripting language such as Perl, Python, or Ruby > would be to do most things you might want to do. If you want to extend a > compiled plug-in that is also possible. > > Take a look at TinyScheme (us

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Amit Kumar Saha
Hello Michael, On 8/21/07, Michael Schumacher <[EMAIL PROTECTED]> wrote: > > Von: "Amit Kumar Saha" <[EMAIL PROTECTED]> > > Should it be more easy than writing e.g. a plug-in in Python? Yes. I am basically targeting end-users of GIMP,mainly GIMP. So learning Python for them might be not the best

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Martin Nordholts
Karl Günter Wünsch wrote: > On Tuesday 21 August 2007, Michael Schumacher wrote: >> Should it be more easy than writing e.g. a plug-in in Python? > How about having a C++ virutal interface which you only have to fill in with > your own methods and GUI elements in a set dialog interface... > I hav

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Kevin Cozens
Amit Kumar Saha wrote: > Is there any way to make GIMP plugins themselves extensible. [snip] > I would appreciate even the slightest of insights. As Michael mentioned, using a scripting language such as Perl, Python, or Ruby would be to do most things you might want to do. If you want to extend a

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Michael J. Hammel
> > Von: "Amit Kumar Saha" <[EMAIL PROTECTED]> > > Is there any way to make GIMP plugins themselves extensible. My point > > here is that, can we make a GIMP plugin which allows itself modifiable > > by a end-user to include a new functionality without much of a hassle > > on part of the end-user.

[Gimp-developer] importing gimp in eclipse

2007-08-21 Thread elekis
hi all, I try to import the project gimp in eclipse (for a work). but that seems more complicated than I though. What I made is the plugin subclipse made a checkout with it on gimp repository and grap the source code. Now , I have all source but I have no idea how to compil them with eclipse .

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Karl Günter Wünsch
On Tuesday 21 August 2007, Michael Schumacher wrote: > Should it be more easy than writing e.g. a plug-in in Python? How about having a C++ virutal interface which you only have to fill in with your own methods and GUI elements in a set dialog interface... I have several things that I really woul

Re: [Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Michael Schumacher
> Von: "Amit Kumar Saha" <[EMAIL PROTECTED]> > Is there any way to make GIMP plugins themselves extensible. My point > here is that, can we make a GIMP plugin which allows itself modifiable > by a end-user to include a new functionality without much of a hassle > on part of the end-user. Does any

[Gimp-developer] Extending GIMP Plugins

2007-08-21 Thread Amit Kumar Saha
Hello all, GIMP plugins extend GIMP, we know that. Is there any way to make GIMP plugins themselves extensible. My point here is that, can we make a GIMP plugin which allows itself modifiable by a end-user to include a new functionality without much of a hassle on part of the end-user. Does any o