/usr/share/gtk-doc/html/libvips/extending.html

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>VIPS Reference Manual: Extending VIPS</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="index.html" title="VIPS Reference Manual">
<link rel="up" href="ch01.html" title="VIPS Overview">
<link rel="prev" href="binding.html" title="Writing bindings for libvips">
<link rel="next" href="ch02.html" title="Core VIPS API">
<meta name="generator" content="GTK-Doc V1.20 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="10"><tr valign="middle">
<td width="100%" align="left" class="shortcuts"></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
<td><a accesskey="u" href="ch01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
<td><a accesskey="p" href="binding.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
<td><a accesskey="n" href="ch02.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
</tr></table>
<div class="refentry">
<a name="extending"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle">Extending VIPS</span></h2>
<p>Extending — How to add operations to VIPS</p>
</td>
<td class="gallery_image" valign="top" align="right"></td>
</tr></table></div>
<div class="refsect1">
<a name="extending-pointtopoint"></a><h2>A simple point-to-point operation</h2>
<p>
      All operations are subclasses of #VipsOperation, which in turn
      subclasses #VipsObject and then %GObject. You need to define a new
      instance struct and a new class struct.

</p>
<pre class="programlisting">
typedef struct _Negative {
  VipsOperation parent_instance;

  VipsImage *in;
  VipsImage *out;

  int image_max;

} Negative;

typedef struct _NegativeClass {
  VipsOperationClass parent_class;

  /* No new class members needed for this op.
   */

} NegativeClass;
</pre>
<p>
    </p>
<p>
      This operation will find the photographic negative of an unsigned
      8-bit image, optionally letting you specify the value which the pixels
      "pivot" about. It doesn't need any class members (ie. values common
      to all operations of this type), so the second struct is empty. See
      vips_invert() for a more complete version of this operation that's
      actually in the library.
    </p>
<p>
      GObject has a handy macro to write some of the boilerplate for you.

</p>
<pre class="programlisting">
G_DEFINE_TYPE( Negative, negative, VIPS_TYPE_OPERATION );
</pre>
<p>

      This defines a function called negative_get_type(),
      which registers this new class and returns its #GType (a
      pointer-sized integer). negative_get_type() in turn needs two
      functions, negative_init(), to initialise a new instance, and
      negative_class_init(), to initialise a new class.
    </p>
<p>
      negative_init() is very simple, it just sets the default value for
      our optional class parameter.

</p>
<pre class="programlisting">
static void
negative_init( Negative *negative )
{
  negative-&gt;image_max = 255;
}
</pre>
<p>
    </p>
<p>
      negative_class_init() is more complicated: it has to set various
      fields in various superclasses.

</p>
<pre class="programlisting">
static void
negative_class_init( NegativeClass *class )
{
  GObjectClass *gobject_class = G_OBJECT_CLASS( class );
  VipsObjectClass *object_class = VIPS_OBJECT_CLASS( class );

  gobject_class-&gt;set_property = vips_object_set_property;
  gobject_class-&gt;get_property = vips_object_get_property;

  object_class-&gt;nickname = "negative";
  object_class-&gt;description = "photographic negative";
  object_class-&gt;build = negative_build;

  VIPS_ARG_IMAGE( class, "in", 1, 
    "Input", 
    "Input image",
    VIPS_ARGUMENT_REQUIRED_INPUT,
    G_STRUCT_OFFSET( Negative, in ) );

  VIPS_ARG_IMAGE( class, "out", 2, 
    "Output", 
    "Output image",
    VIPS_ARGUMENT_REQUIRED_OUTPUT, 
    G_STRUCT_OFFSET( Negative, out ) );

  VIPS_ARG_INT( class, "image_max", 4, 
    "Image maximum", 
    "Maximum value in image: pivot about this",
    VIPS_ARGUMENT_OPTIONAL_INPUT,
    G_STRUCT_OFFSET( Negative, image_max ),
    0, 255, 255 );
}
</pre>
<p>
    </p>
<p>
      In %GObject, it needs to set the getters and setters for this class. vips
      has a generic get/set system, so any subclass of #VipsObject needs to
      use the vips ones.
    </p>
<p>
      In #VipsObject, it needs to set the operation @nickname and @description,
      and set a build function (see below). @nickname is used to refer to
      this operation in the API, @description is used to explain this
      operation to users and will be translated into their language.
    </p>
<p>
      Finally, it needs to set the arguments this class constructor
      takes. There are a set of handy macros for doing this. The first few
      parameters are always the same and mean: class pointer for argument,
      argument name, argument priority (bindings expect required arguments in
      order of priority), long argument name (this one is internationalised
      and displayed to users), description (again, users can see this),
      some flags describing the argument, and finally the position of the
      member in the struct.
    </p>
<p>
      Integer arguments take three more values: the minimum, maximum and
      default value for the argument.
    </p>
<p>
      The build function is the thing VipsObject calls after supplying
      arguments. It checks that all required arguments have been set and are
      valid and constructs the object. After build, the object is expected
      to be ready for use.

</p>
<pre class="programlisting">
static int
negative_build( VipsObject *object )
{
  VipsObjectClass *class = VIPS_OBJECT_GET_CLASS( object );
  Negative *negative = (Negative *) object;

  if( VIPS_OBJECT_CLASS( negative_parent_class )-&gt;build( object ) )
    return( -1 );

  if( vips_check_uncoded( class-&gt;nickname, negative-&gt;in ) ||
    vips_check_format( class-&gt;nickname, negative-&gt;in, VIPS_FORMAT_UCHAR ) )
    return( -1 );

  g_object_set( object, "out", vips_image_new(), NULL ); 

  if( vips_image_pipelinev( negative-&gt;out, 
    VIPS_DEMAND_STYLE_THINSTRIP, negative-&gt;in, NULL ) )
    return( -1 );

  if( vips_image_generate( negative-&gt;out, 
    vips_start_one, 
    negative_generate, 
    vips_stop_one, 
    negative-&gt;in, negative ) )
    return( -1 );

  return( 0 );
}
</pre>
<p>
    </p>
<p>
      negative_build() first chains up to the superclass: this will check
      that all input arguments have been supplied and are sane.
    </p>
<p>
      Next, it adds its own checks. This is a demo operation, so we just
      work for uncoded, unsigned 8-bit images.
    </p>
<p>
      Next, it creates the output image. This needs to be set with
      g_object_set() so that vips can see that it has been assigned. vips
      will also handle the reference counting for you.
    </p>
<p>
      vips_image_pipelinev() links our new image onto the input image and
      notes that this operation prefers to work in lines.
    </p>
<p>
      Finally, vips_image_generate() attaches a set of callbacks to the
      output image to generate chunks of it on request. vips_start_one()
      and vips_stop_one() are convenience functions that make the input
      region for you.
    </p>
<p>
      And then the actual image processing.

</p>
<pre class="programlisting">
static int
negative_generate( VipsRegion *or, 
  void *vseq, void *a, void *b, gboolean *stop )
{
  /* The area of the output region we have been asked to make.
   */
  VipsRect *r = &amp;or-&gt;valid;

  /* The sequence value ... the thing returned by vips_start_one().
   */
  VipsRegion *ir = (VipsRegion *) vseq;

  Negative *negative = (Negative *) b;
  int line_size = r-&gt;width * negative-&gt;in-&gt;Bands; 

  int x, y;

  /* Request matching part of input region.
   */
  if( vips_region_prepare( ir, r ) )
    return( -1 );

  for( y = 0; y &lt; r-&gt;height; y++ ) {
    unsigned char *p = (unsigned char *)
      VIPS_REGION_ADDR( ir, r-&gt;left, r-&gt;top + y ); 
    unsigned char *q = (unsigned char *)
      VIPS_REGION_ADDR( or, r-&gt;left, r-&gt;top + y ); 

    for( x = 0; x &lt; line_size; x++ ) 
      q[x] = negative-&gt;image_max - p[x];
  }

  return( 0 );
}
</pre>
<p>
    </p>
<p>
      This has to calculate a section of the output image. The output
      #VipsRegion, @or, contains a #VipsRect called @valid which is the
      area needing calculation. negative_generate() asks for the
      corresponding pixels from the input region, then loops over the
      area. VIPS_REGION_ADDR() is a simple macro that does pointer arithmetic
      for you: you need to stay within the valid area.
    </p>
<p>
      To add the operation to vips, just call negative_get_type(). You
      can then use @negative from any of the vips interfaces. For example,
      in Python you'd use it like this:

</p>
<pre class="programlisting">
out = in.negative(image_max = 128)
</pre>
<p>
    </p>
<p>
      From the command-line it'd look like this:

</p>
<pre class="programlisting">
$ vips negative in.png out.tif --image-max 128
</pre>
<p>
    </p>
<p>
      And from C like this:

</p>
<pre class="programlisting">
VipsImage *in;
VipsImage *out;
if( vips_call( "negative", in, &amp;out, "image_max", 128, NULL ) )
  ... error
</pre>
<p>
    </p>
<p>
      Unfortunately that will do almost no compile-time type checking,
      so all vips operations have a tiny extra wrapper to add a bit of
      safety. For example:

</p>
<pre class="programlisting">
static int 
negative( VipsImage *in, VipsImage **out, ... )
{
  va_list ap;
  int result;

  va_start( ap, out );
  result = vips_call_split( "negative", ap, in, out );
  va_end( ap );

  return( result );
}
</pre>
<p>
    </p>
<p>
      And now you can write:

</p>
<pre class="programlisting">
if( negative( in, &amp;out, "image_max", 128, NULL ) )
  ... error
</pre>
<p>

      and it's at least a bit safer.
    </p>
</div>
<div class="refsect1">
<a name="extending-othertypes"></a><h2>Other types of operation</h2>
<p>
      Change the _build() function to make other types of operation. 
    </p>
<p>
      Use vips_image_generate() with vips_start_many() to make operations 
      which demand pixels from more than one image at once, such as image 
      plus image. 
    </p>
<p>
      Use vips_sink() instead of vips_image_generate() to loop over an image 
      and calculate a value. vips uses this for the statistics operations, 
      like vips_avg().
    </p>
<p>
      Use vips_image_wio_input() to get an entire image into memory so you
      can read it with a pointer. This will obviously not scale well to
      very large images, but some operations, like FFTs or flood-fill, need 
      the whole image to be available at once.
    </p>
<p>
      Make area operations, like filters, by enlarging the #VipsRect that
      _generate() is given before calling vips_image_prepare(). You can
      enlarge the input image, so that the output image is the same size as
      the original input, by using vips_embed() within the _build() function.
    </p>
<p>
      Make things like flips and rotates by making larger changes to the
      #VipsRect in _generate().
    </p>
<p>
      Make zero-copy operations, like vips_insert(), with vips_region_region().
    </p>
</div>
</div>
<div class="footer">
<hr>
          Generated by GTK-Doc V1.20</div>
</body>
</html>
libvips-doc 7.40.6-2 / usr / share / gtk-doc / html / libvips / extending.html
