moved all of the docbook sources to xml/
cleaned up the makefile for the changes
--- a/docs/specification/Makefile Tue Aug 11 02:18:06 2009 -0500
+++ b/docs/specification/Makefile Tue Aug 11 03:35:18 2009 -0500
@@ -1,18 +1,21 @@
TRANSFORM_OPTS=--nonet --xinclude
-spec.stamp: $(SOURCES) $(SHEET)
- $(TRANSFORM) $(TRANSFORM_OPTS) -o $(OUTPUT) $(SHEET) $(BOOK)
+all: xml/xml.stamp $(SHEETS) $(BOOK_SOURCES) - rm -rf $(OUTPUT) spec.stamp
+ rm -rf $(OUTPUT) xml/xml.stamp dir.stamp $(BOOK_BUILT_SOURCES) +xml/xml.stamp: $(BOOK_SOURCES) $(BOOK_BUILT_SOURCES) sheets/gf_spec.xsl + $(TRANSFORM) $(TRANSFORM_OPTS) -o $(OUTPUT) sheets/gf_spec.xsl $(BOOK) --- a/docs/specification/clients.xml Tue Aug 11 02:18:06 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,34 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
- <refentrytitle>Clients</refentrytitle>
- <refmiscinfo>Clients</refmiscinfo>
- <refsect2 id="feedclient">
- <title>Feed Clients</title>
- Feed clients simply provide a group of possible notifications.
- This could be anything from Galago for presence notification,
- to syslog to let you know of critical system events.
- <refsect2 id="notifierclient">
- <title>Notifier Clients</title>
- Notifier clients are responsible for presenting the
- notifications to the user and for providing the user a way to
--- a/docs/specification/communication.xml Tue Aug 11 02:18:06 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,19 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
-<refentry id="communication">
- <refentrytitle>Communication</refentrytitle>
- <refmiscinfo>Communication in the Guifications Framework</refmiscinfo>
- <title>Communication Overview</title>
- Guifications using the typical client/server model for
- communication. However, there are a few
--- a/docs/specification/daemon.xml Tue Aug 11 02:18:06 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
- <refentrytitle>Server</refentrytitle>
- <refmiscinfo>Guifications Daemon</refmiscinfo>
- <title>Overview</title>
- The Guifications framework is based around one or more daemons.
- The daemon is responsible for everything except presentation. It
- manages connections, provides a central point for preferences,
- routes notifications, and keeps itself in sync with other daemons
- if your notification pool.
\ No newline at end of file
--- a/docs/specification/gf_spec.xml Tue Aug 11 02:18:06 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
- "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd">
-<book id="gf_spec" xmlns:xi="http://www.w3.org/2003/XInclude">
- <title>Guifications Specification</title>
- <releaseinfo>$Id$</releaseinfo>
- Guifications 3 is a framework for integrating a powerful
- notification system into absolutely anything. The main driving
- force behind Guifications 3 is the library gflib. This library
- contains all of the basic objects for any an all Guifications
- The framework has been designed to be as neutral as possible for
- not only desktops, but platforms as well. It provides the basic
- behavior and leaves the implementation up for whatever platform
- it may be used on. This is accomplished by abstraction for
- inter-process communication, user interfaces, and preferences.
- <title>Overview</title>
- <xi:include href="communication.xml"/>
--- a/docs/specification/gf_spec.xsl Tue Aug 11 02:18:06 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
- <!-- import the chunked XSL stylesheet -->
- <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl"/>
- <!-- change some parameters -->
- <xsl:param name="chunker.ouput.indent" select="'yes'"/>
- <xsl:param name="html.ext" select="'.html'"/>
- <xsl:param name="refentry.generate.name" select="0"/>
- <xsl:param name="refentry.generate.title" select="1"/>
- <xsl:param name="use.id.as.filename" select="1"/>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/sheets/gf_spec.xsl Tue Aug 11 03:35:18 2009 -0500
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="utf-8"?> +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> + <!-- import the chunked XSL stylesheet --> + <xsl:import href="http://docbook.sourceforge.net/release/xsl/current/html/chunk.xsl"/> + <!-- change some parameters --> + <xsl:param name="chunker.ouput.indent" select="'yes'"/> + <xsl:param name="html.ext" select="'.html'"/> + <xsl:param name="refentry.generate.name" select="0"/> + <xsl:param name="refentry.generate.title" select="1"/> + <xsl:param name="use.id.as.filename" select="1"/> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/xml/clients.xml Tue Aug 11 03:35:18 2009 -0500
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> + <refentrytitle>Clients</refentrytitle> + <refmiscinfo>Clients</refmiscinfo> + <refsect2 id="feedclient"> + <title>Feed Clients</title> + Feed clients simply provide a group of possible notifications. + This could be anything from Galago for presence notification, + to syslog to let you know of critical system events. + <refsect2 id="notifierclient"> + <title>Notifier Clients</title> + Notifier clients are responsible for presenting the + notifications to the user and for providing the user a way to --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/xml/communication.xml Tue Aug 11 03:35:18 2009 -0500
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> +<refentry id="communication"> + <refentrytitle>Communication</refentrytitle> + <refmiscinfo>Communication in the Guifications Framework</refmiscinfo> + <title>Communication Overview</title> + Guifications using the typical client/server model for + communication. However, there are a few --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/xml/daemon.xml Tue Aug 11 03:35:18 2009 -0500
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> + <refentrytitle>Server</refentrytitle> + <refmiscinfo>Guifications Daemon</refmiscinfo> + <title>Overview</title> + The Guifications framework is based around one or more daemons. + The daemon is responsible for everything except presentation. It + manages connections, provides a central point for preferences, + routes notifications, and keeps itself in sync with other daemons + if your notification pool. \ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/xml/gf_spec.xml Tue Aug 11 03:35:18 2009 -0500
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"> +<book id="gf_spec" xmlns:xi="http://www.w3.org/2003/XInclude"> + <title>Guifications Specification</title> + Guifications 3 is a framework for integrating a powerful + notification system into absolutely anything. The main driving + force behind Guifications 3 is the library gflib. This library + contains all of the basic objects for any an all Guifications + The framework has been designed to be as neutral as possible for + not only desktops, but platforms as well. It provides the basic + behavior and leaves the implementation up for whatever platform + it may be used on. This is accomplished by abstraction for + inter-process communication, user interfaces, and preferences. + <title>Overview</title> + <xi:include href="communication.xml"/>