restructure source code tree in order to be more managable, handle "wider" and "narrower" text specifications

1 files changed, 22 insertions, 9 deletions

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 <glib/gtypes.h>
+
+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