Re: [Gimp-developer] Non-interactive plug-in calls (cross-posted to comp.graphics.apps.gimp)

2002-02-10 Thread Cindy Huyser

Yep, that was the problem.  Thanks, Sven!

Cindy

Sven Neumann wrote:

> as a quick guess, I'd say you need to call "plug_in_c_astretch" since
> that's how the plug-in is internally registered. Most documentation is
> using hyphens here but that's just because most documentation deals
> with Script-Fu which needs hyphens instead of underscores.  However I
> wonder why you are getting GIMP_PDB_EXECUTION_ERROR, since that should
> be GIMP_PDB_CALLING_ERROR then.
> 
> Salut, Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Re: [Gimp-user] Opening Photoshop Files

2002-02-10 Thread Leonard Rosenthol

At 12:41 PM 2/8/2002 +0100, Sven Neumann wrote:
>Leonard Rosenthol <[EMAIL PROTECTED]> writes:
>
> >   Will it still use FreeType for the actual rendering of the
> > glyphs?  And if not, then what?
>
>yes, it will use Freetype2 but somewhat hidden behind a Pango layer.

 Excellent!!


>The advantage of using Pango on top of Freetype2 is that it takes care
>of all the ugly details of glyph positioning and shaping.

 Yup, Pango is great stuff and definitely the way to go.  That 
should make for some VERY NICE text support in future Gimps.Now you'll 
just have to support PSD Text Layers ;).


LDR

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



Re: [Gimp-developer] Non-interactive plug-in calls (cross-posted to comp.graphics.apps.gimp)

2002-02-10 Thread Sven Neumann

Hi,

Cindy Huyser <[EMAIL PROTECTED]> writes:

> // Call the desired plug-in --  returns GIMP_PDB_EXECUTION_ERROR
> return_vals = gimp_run_procedure("plug-in-c-astretch",   
> &nreturn_vals,
> GIMP_PDB_INT32,
> GIMP_RUN_NONINTERACTIVE,
> GIMP_PDB_IMAGE, imageID,
> GIMP_PDB_DRAWABLE,
> bg_drawable->id,
> GIMP_PDB_END); 
> 
> Any insight you'd be able to lend on this problem would be greatly
> appreciated!

as a quick guess, I'd say you need to call "plug_in_c_astretch" since
that's how the plug-in is internally registered. Most documentation is
using hyphens here but that's just because most documentation deals
with Script-Fu which needs hyphens instead of underscores.  However I
wonder why you are getting GIMP_PDB_EXECUTION_ERROR, since that should
be GIMP_PDB_CALLING_ERROR then.


Salut, Sven

___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] Non-interactive plug-in calls (cross-posted to comp.graphics.apps.gimp)

2002-02-10 Thread Cindy Huyser

Here's a newbie question about non-interactive plug-in calls:

I'm writing a (C) plug-in in which I intend to call another plug-in
non-interactively prior to doing my own processing.  I copy the active
layer, and since the images I'm dealing with all have an alpha channel I
make sure I'm dealing with the image background (rather than the alpha
mask); I then grab the drawable and image IDs from the scratch layer,
and then call a plug-in non-interactively.  

I know my drawable is good, as I've succeeded in doing all the desired
processing after the plug-in call. In every plug-in that I've tried,
though, GIMP_PDB_EXECUTION_ERROR is returned from the plug-in call (I've
checked the plug-ins against the image to make sure that they work on
the image before I try
the call).

Here's the skeleton of my code around the non-interactive call:

activeLayer = gimp_image_get_active_layer(image);
workingLayer = gimp_layer_copy(activeLayer);
add_OK = gimp_image_add_layer(image, workingLayer, -1); 

if((gimp_layer_get_edit_mask(workingLayer)))
setMaskOK = gimp_layer_set_edig_mask(workingLayer, 0);   

bg_drawable = gimp_drawable_get(workingLayer); 
imageID = gimp_drawable_image(bg_drawable->id);


// Call the desired plug-in --  returns GIMP_PDB_EXECUTION_ERROR
return_vals = gimp_run_procedure("plug-in-c-astretch",   
&nreturn_vals,
GIMP_PDB_INT32,
GIMP_RUN_NONINTERACTIVE,
GIMP_PDB_IMAGE, imageID,
GIMP_PDB_DRAWABLE,
bg_drawable->id,
GIMP_PDB_END); 

Any insight you'd be able to lend on this problem would be greatly
appreciated!

Thanks,
Cindy Huyser
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] Re: [Gimp-user] Opening Photoshop Files

2002-02-10 Thread Sven Neumann

Hi,

Dov Grobgeld <[EMAIL PROTECTED]> writes:

> Hebrew with vowel positioning has also been ported by me to ft2.
> 
> See
> http://imagic.weizmann.ac.il/~dov/Hebrew/pango-hebrew.html
> http://imagic.weizmann.ac.il/~dov/freesw/paps
> 
> for some screen shots and utilities.

oh, I wasn't aware of that. Most probably I missed the hebrew-ft2
module because it is not listed in Pango's configure.in. Perhaps
you could correct that.


Salut, Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] ANNOUNCE: GIMP 1.3.3

2002-02-10 Thread Sven Neumann

Hi,

if you die for crashing, unstable software, if you like to spend your
nights fighting with the compiler, then it's time to get your hands on
the latest release in the unstable 1.3 series of The GIMP:

  ftp://ftp.gimp.org/pub/gimp/v1.3/v1.3.3/

This release depends on:

  glib-1.3.13
  pango-0.24 (with FT2 support)
  atk-0.10
  gtk+-1.3.13


Overview of Changes in GIMP 1.3.3
=
- Most of the code is free of deprecated GTK+ calls now [Mitch, Yosh, Sven]
- More use of stock icons [Sven, Mitch]
- New RGB->Indexed quantizer [Adam]
- Framework for pluggable tools [Nathan]
- More tool system cleanups [Mitch]
- Improved image status bar [Mitch]
- GimpObjects now know their memory footprint [Mitch]
- GimpUnit cleanup [Sven]
- Message proofreading [Bex]
- configure.in should work with autoconf-2.5 [Raja R Harinath]
- Bugfixes
- More stuff not mentioned here (see the ChangeLog)

Other Contributors:
  Simon Budig


Happy GIMPing,

Sven Neumann
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] Re: [Gimp-user] Opening Photoshop Files

2002-02-10 Thread Dov Grobgeld

Hebrew with vowel positioning has also been ported by me to ft2.

See
http://imagic.weizmann.ac.il/~dov/Hebrew/pango-hebrew.html
http://imagic.weizmann.ac.il/~dov/freesw/paps

for some screen shots and utilities.

Regards,
Dov

On Sun, Feb 10, 2002 at 07:22:09PM +0100, Sven Neumann wrote:
> Hi,
> 
> Dov Grobgeld <[EMAIL PROTECTED]> writes:
> 
> > > yes, it will use Freetype2 but somewhat hidden behind a Pango layer.
> > > The advantage of using Pango on top of Freetype2 is that it takes care
> > > of all the ugly details of glyph positioning and shaping.
> > 
> > And you get all the beautiful rendering of lots of exotic scripts!
> > Imagine, now you will be able to render your APL programs in Gimp
> > with comments in Chinese and Runes intermixed. 8-)
> > 
> > This is really the way to go! Keep it up.
> 
> uhm, yes, that's the plan. The reality is however that PangoFT2 at the
> moment has the basic shaper which works well for lots of scripts but
> not so well for the more exotic ones. Then there's an arabic shaper
> that's been added in the latest release and that's it. If we want all
> the exotic scripts to render correctly, someone needs to port more
> PangoXft shaper modules to PangoFT2. Fortunately the porting is pretty
> straightforward.
> 
> 
> Salut, Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] Re: [Gimp-user] Opening Photoshop Files

2002-02-10 Thread Sven Neumann

Hi,

Dov Grobgeld <[EMAIL PROTECTED]> writes:

> > yes, it will use Freetype2 but somewhat hidden behind a Pango layer.
> > The advantage of using Pango on top of Freetype2 is that it takes care
> > of all the ugly details of glyph positioning and shaping.
> 
> And you get all the beautiful rendering of lots of exotic scripts!
> Imagine, now you will be able to render your APL programs in Gimp
> with comments in Chinese and Runes intermixed. 8-)
> 
> This is really the way to go! Keep it up.

uhm, yes, that's the plan. The reality is however that PangoFT2 at the
moment has the basic shaper which works well for lots of scripts but
not so well for the more exotic ones. Then there's an arabic shaper
that's been added in the latest release and that's it. If we want all
the exotic scripts to render correctly, someone needs to port more
PangoXft shaper modules to PangoFT2. Fortunately the porting is pretty
straightforward.


Salut, Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer



[Gimp-developer] Re: Re: [Gimp-user] Opening Photoshop Files

2002-02-10 Thread Dov Grobgeld

On Fri, Feb 08, 2002 at 12:41:42PM +0100, Sven Neumann wrote:
> 
> yes, it will use Freetype2 but somewhat hidden behind a Pango layer.
> The advantage of using Pango on top of Freetype2 is that it takes care
> of all the ugly details of glyph positioning and shaping.

And you get all the beautiful rendering of lots of exotic scripts!
Imagine, now you will be able to render your APL programs in Gimp
with comments in Chinese and Runes intermixed. 8-)

This is really the way to go! Keep it up.

Regards,
Dov
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer