after a cvs (anonymous cvs) update last morning:
Making all in libgimp
make[2]: Entering directory /home/olivier/inst/cvsgimp/gimp/libgimp'
make[2]: *** No rule to make target `gimpgradientedit_pdb.c', needed by
`gimpgradientedit_pdb.lo'. Stop.
make[2]: Leaving directory /home/olivier/inst/cvsgim
On Fri, Oct 01, 2004 at 09:43:29AM +0200, Olivier wrote:
> after a cvs (anonymous cvs) update last morning:
>
> Making all in libgimp
> make[2]: Entering directory /home/olivier/inst/cvsgimp/gimp/libgimp'
> make[2]: *** No rule to make target `gimpgradientedit_pdb.c', needed by
> `gimpgradientedit
Hi,
a while ago I posted a list here with things that should be addressed
before we can start doing pre-releases for 2.2. Let's have a look at
what we achieved in the meantime.
> Scale/Resize dialogs
>
> We definitely need to redo these. The changes to the File->New
> dialog and to the intern
On Friday 01 October 2004 10:46, Sven Neumann wrote:
> > Python bindings
> >
> > IMO we should move pygimp out of the gimp tree into a
> > gimp-python package. That would make it easier to give it a
> > proper python-like build environment and would make it easier for
> > packagers. Yosh also had
Hi,
"Joao S. O. Bueno Calligaris" <[EMAIL PROTECTED]> writes:
> Another thing IMHO is important, although marked as low priority in
> bugzilla is exposing the full options for the transform tools in the
> PDB - BUG 137053
> ( http://bugzilla.gnome.org/show_bug.cgi?id=137053 )
> That would mak
The fix included with Gimp 2.0.5 ("work around file-descriptor leak in
Pango (#143542, #148997)") appears to have resolved most of the memory
leak issues I was running into with my Gimp Perl scripts and the
gimp_text_fontname function (thanks to those involved!). I do still
notice a memory increas
