From 15b0f5ffbabe57bc2181e80996fff23acce9b6d0 Mon Sep 17 00:00:00 2001 From: Dom Lachowicz Date: Wed, 8 Jan 2003 21:24:33 +0000 Subject: restructure source code tree in order to be more managable, handle "wider" and "narrower" text specifications --- rsvg-defs.h | 31 ++++++++++++++++++++++--------- 1 file changed, 22 insertions(+), 9 deletions(-) (limited to 'rsvg-defs.h') diff --git a/rsvg-defs.h b/rsvg-defs.h index 28bb0f57..055f35cb 100644 --- a/rsvg-defs.h +++ b/rsvg-defs.h @@ -1,21 +1,30 @@ +/* vim: set sw=4: -*- Mode: C; tab-width: 4; indent-tabs-mode: t; c-basic-offset: 4 -*- */ + +#ifndef RSVG_DEFS_H +#define RSVG_DEFS_H + /* A module for handling SVG defs */ +#include + +G_BEGIN_DECLS + typedef struct _RsvgDefs RsvgDefs; typedef struct _RsvgDefVal RsvgDefVal; typedef enum { - /* todo: general question: should this be high level, ie a generic - paint server, coupled with a paint server interface; or low level, - ie specific definable things? For now, we're going low level, - but it's not clear that's the best way to go. */ - RSVG_DEF_LINGRAD, - RSVG_DEF_RADGRAD, - RSVG_DEF_PATTERN + /* todo: general question: should this be high level, ie a generic + paint server, coupled with a paint server interface; or low level, + ie specific definable things? For now, we're going low level, + but it's not clear that's the best way to go. */ + RSVG_DEF_LINGRAD, + RSVG_DEF_RADGRAD, + RSVG_DEF_PATTERN } RsvgDefType; struct _RsvgDefVal { - RsvgDefType type; - void (*free) (RsvgDefVal *self); + RsvgDefType type; + void (*free) (RsvgDefVal *self); }; RsvgDefs * @@ -29,3 +38,7 @@ rsvg_defs_set (RsvgDefs *defs, const char *name, RsvgDefVal *val); void rsvg_defs_free (RsvgDefs *defs); + +G_END_DECLS + +#endif -- cgit v1.2.1