On Mon, 2003-09-29 at 14:42, Sven Neumann wrote:
> Hi,
>
> Perhaps you want to contribute a short porting guide. Such a document
> should be included with the 1.3 API reference. Let me know if you are
> interested, I can give you a template that we can include in
> devel-docs/libgimp later.
Now
At 09:44 28.09.03 -0700, Jeff Trefftzs wrote:
>Hi all,
>
>As we are about to move to the next stage of gimpery, I have begun
>looking closely at my large collection of plug-ins, many of which I
>remember compiling with GIMP_ENABLE_COMPAT_CRUFT, and wondering how to
>make them usable again under the
Hi,
Jeff Trefftzs <[EMAIL PROTECTED]> writes:
> On Mon, 2003-09-29 at 06:44, Sven Neumann wrote:
>
> > If your plug-in still needs GIMP_ENABLE_COMPAT_CRUFT, it hasn't been
> > ported to gimp-1.2 yet. Of course you need to do that first.
> >
>
> Do I need to do anything except replace the old c
On Mon, 2003-09-29 at 06:44, Sven Neumann wrote:
> If your plug-in still needs GIMP_ENABLE_COMPAT_CRUFT, it hasn't been
> ported to gimp-1.2 yet. Of course you need to do that first.
>
Do I need to do anything except replace the old cruft with the new calls
as specified in gimp-1.2.5/libgimp/gim
Hi,
Jeff Trefftzs <[EMAIL PROTECTED]> writes:
> Hi all,
>
> As we are about to move to the next stage of gimpery, I have begun
> looking closely at my large collection of plug-ins, many of which I
> remember compiling with GIMP_ENABLE_COMPAT_CRUFT, and wondering how
> to make them usable again u
Hi Jeff,
Jeff Trefftzs wrote:
> As we are about to move to the next stage of gimpery, I have begun
> looking closely at my large collection of plug-ins, many of which I
> remember compiling with GIMP_ENABLE_COMPAT_CRUFT, and wondering how to
> make them usable again under the new regime. Can anyb
