Re: [Gimp-developer] SoC project ideas

2007-03-14 Thread Sven Neumann
Hi, On Wed, 2007-03-14 at 13:41 +0300, Alexandre Prokoudine wrote: > Related entry is: http://bugzilla.gnome.org/show_bug.cgi?id=119874 It would be useful, perhaps even necessary, to also address bug 330099: http://bugzilla.gnome.org/show_bug.cgi?id=330099 Sven __

Re: [Gimp-developer] memory manage in python-fu

2007-03-14 Thread Sven Neumann
Hi, On Wed, 2007-03-14 at 09:01 -0700, William Skaggs wrote: > It might help if I explain a little more about how GIMP handles > memory. GIMP does not rely on the operating system for swapping. > When you start GIMP, it creates a file, of fixed size which you > designate in the Preferences, to s

Re: [Gimp-developer] Tools

2007-03-14 Thread William Skaggs
From: Federico Alcantara <[EMAIL PROTECTED]> >I am interested in knowning if Gimp is written in >C/C++, and which tools are needed to compile, debug, >and test it? You can find a brief overview at http://wiki.gimp.org/gimp/SummerOfCode and a lot more detailed information at http://developer

Re: [Gimp-developer] Tools

2007-03-14 Thread Tor Lillqvist
Federico Alcantara writes: > I am interested in knowning if Gimp is written in C/C++, There is no programming language called C/C++. GIMP is written in C. It can be scripted in Scheme (a dialect of Lisp), and the usual suspects Perl and Python. > and which tools are needed to compile, debug,

Re: [Gimp-developer] Tools

2007-03-14 Thread Michael Natterer
On Wed, 2007-03-14 at 12:47 -0700, Federico Alcantara wrote: > Hi > > I am interested in knowning if Gimp is written in > C/C++, and which tools are needed to compile, debug, > and test it? What about downloading it and checking yourself? ciao, --mitch __

[Gimp-developer] Tools

2007-03-14 Thread Federico Alcantara
Hi I am interested in knowning if Gimp is written in C/C++, and which tools are needed to compile, debug, and test it? Federico Alcantara Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & D

Re: [Gimp-developer] memory manage in python-fu

2007-03-14 Thread Frédéric
On Wednesday 14 March 2007 17:01, William Skaggs wrote: > It might help if I explain a little more about how GIMP handles > memory.  GIMP does not rely on the operating system for swapping. > When you start GIMP, it creates a file, of fixed size which you > designate in the Preferences, to serve a

Re: [Gimp-developer] how to call a plugin

2007-03-14 Thread Luis A. Florit
Hi Bill, > >Now, I just want to blur my drawable from my plugin. > >I tried this: > > > > GimpParam *rreturn_vals; > > gint nnreturn_vals; > > rreturn_vals = gimp_run_procedure("plug_in_blur", &nnreturn_vals, > > GIMP_PDB_INT32, GIMP_RUN_NONINTERACTIVE, > >

Re: [Gimp-developer] memory manage in python-fu

2007-03-14 Thread Alexandre Prokoudine
On 3/14/07, William Skaggs wrote: > What is happening to you is that the swap file is filling up, > because data is accumulating there that ought to be cleared > away. btw, is it possible to provide some feedback to users that available resources are getting pretty close to zero? Alexandre _

Re: [Gimp-developer] memory manage in python-fu

2007-03-14 Thread William Skaggs
> [...] The thing I did not >expect was that it had well over a gig of ram left unused, no swap used, >30 gig of unused drive, and it still thought the hard drive was full. > [...] It might help if I explain a little more about how GIMP handles memory. GIMP does not rely on the operating syst

Re: [Gimp-developer] how to call a plugin

2007-03-14 Thread William Skaggs
Luis Florit wrote: >Now, I just want to blur my drawable from my plugin. >I tried this: > > GimpParam *rreturn_vals; > gint nnreturn_vals; > rreturn_vals = gimp_run_procedure("plug_in_blur", &nnreturn_vals, > GIMP_PDB_INT32, GIMP_RUN_NONINTERACTIVE, >

[Gimp-developer] how to call a plugin

2007-03-14 Thread Luis A. Florit
Pals, I am feeling so silly in trying to develop a plugin... I am stalling even at the most easy tasks. Now, I just want to blur my drawable from my plugin. I tried this: GimpParam *rreturn_vals; gint nnreturn_vals; rreturn_vals = gimp_run_procedure("plug_in_blur", &nnr

Re: [Gimp-developer] SoC project ideas

2007-03-14 Thread Alexandre Prokoudine
On 3/14/07, Aurimas Juška wrote: > I think that's a very nice idea. In addition to this, a way of > organizing resources (brushes, gradients, etc) in collections could be > introduced. They could be stored in a single file, so that user could > easily share, install or remove many resources in a s

Re: [Gimp-developer] SoC project ideas

2007-03-14 Thread Aurimas Juška
Hi, On 3/9/07, Joao S. O. Bueno Calligaris <[EMAIL PROTECTED]> wrote: > * Categories for brushes, fonts, gradients and palettes > > If one adds too many fonts or brushes to GIMP, they quickly become > un-manageable through the existing UI. Implementing a way of > organizing these resources in s