removed the specification directory
moved it's contents to it's parent directory
renamed the guifications3 directory to specification
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/Makefile Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,18 @@
+TRANSFORM_OPTS=--nonet --xinclude +spec.stamp: $(SOURCES) $(SHEET) + $(TRANSFORM) $(TRANSFORM_OPTS) -o $(OUTPUT) $(SHEET) $(BOOK) + rm -rf $(OUTPUT) spec.stamp --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/clients.xml Tue Aug 11 02:18:06 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/communication.xml Tue Aug 11 02:18:06 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/daemon.xml Tue Aug 11 02:18:06 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/gf_spec.xml Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,36 @@
+<?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"/> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/specification/gf_spec.xsl Tue Aug 11 02:18:06 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"/> --- a/docs/specifications/guifications3/Makefile Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,18 +0,0 @@
-TRANSFORM_OPTS=--nonet --xinclude-spec.stamp: $(SOURCES) $(SHEET)- $(TRANSFORM) $(TRANSFORM_OPTS) -o $(OUTPUT) $(SHEET) $(BOOK)- rm -rf $(OUTPUT) spec.stamp--- a/docs/specifications/guifications3/clients.xml Mon Aug 03 02:48:50 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/specifications/guifications3/communication.xml Mon Aug 03 02:48:50 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/specifications/guifications3/daemon.xml Mon Aug 03 02:48:50 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/specifications/guifications3/gf_spec.xml Mon Aug 03 02:48:50 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/specifications/guifications3/gf_spec.xsl Mon Aug 03 02:48:50 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"/>--- a/docs/specifications/themes/Makefile Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,21 +0,0 @@
-TRANSFORM_OPTS=--nonet --xinclude-spec.stamp: $(SOURCES) $(SHEET)- $(TRANSFORM) $(TRANSFORM_OPTS) -o $(OUTPUT) $(SHEET) $(BOOK)- rm -rf $(OUTPUT) spec.stamp--- a/docs/specifications/themes/about.xml Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,33 +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>About</refentrytitle>- <refmiscinfo>About the Notification Theme Specification</refmiscinfo>- Notifications and themes go hand in hand when being displayed to- an end user. But with three different notification frameworks- being actively developed, why should there be a need for three- different themes for the same application? That is the main- question that this specification is going to attack, and present- a solution that all three projects:- <ulink url="http://www.guifications.org">Guifications</ulink>,- <ulink url="http://galago-project.org">Notification Daemon</ulink>,- and <ulink url="http://growl.info">Growl</ulink> can agree on and- By agreeing to this specification, it is by no means a contract to- only use or implement themes in this fashion, but to make a better- experience with the end users and theme developers.--- a/docs/specifications/themes/history.xml Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,42 +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>History</refentrytitle>- <refmiscinfo>Notification Themes History</refmiscinfo>- <title>History of Notifications Themes</title>- Each project has had unique experiences with their attempts to- implement themes. As such we feel it beneficial to discuss them- here to explain why we are looking for a specific format to adopt.- <title>Guifications</title>- Themes were initially introduced in Guifications 2.x to combat- a growing problem that Gary Kramlich saw; In Guifications 1.x- users had the ability to customize the background image and the- text seen in the notifications. This meant, that for someone- to have the same or similiar notifications as another, that- they would have to copy their settings manually. This was- unacceptable. Thus a theme format was created.- It was aparent around the time of Guifications 2.4 that the- theme format would not scale to quite what Gary wanted.- Unfortunately, due to the amount of 3rd party themes already- created, it was decided that the necessary changes would go- into Guifications 3 rather than a Guifications 2.x release.--- a/docs/specifications/themes/prerequisites.xml Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,41 +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>Prerequisites</refentrytitle>- <refmiscinfo>Prerequisites that need to be considered</refmiscinfo>- <title>Prerequisites</title>- Each notification engine/frame work has their own goals and- expectations of themes. As such, there are all stated here.- <title>Guifications</title>- Guifications is a bit more complicated than Notification- Daemon and Growl. Because of this, the expectations of the- Guifications developers, for what they want to see in this- specification are a bit more indepth.- <title>Notification Daemon</title>--- a/docs/specifications/themes/structure.xml Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,28 +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">-<chapter id="structure">- <title>Structure of a Notification</title>- Each notification engine/frame work has their own goals and- expectations of themes. As such, there are all stated here.- <sect1 id="attributes">- <title>Attributes</title>- Each notification will have a summary/title that will give a- general synopsis of what the notification is for.--- a/docs/specifications/themes/themes.xml Mon Aug 03 02:48:50 2009 -0500
+++ /dev/null Thu Jan 01 00:00:00 1970 +0000
@@ -1,14 +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="notification_themes" xmlns:xi="http://www.w3.org/2003/XInclude">- <title>Notification Theme Specification</title>- <releaseinfo>$Id$</releaseinfo>- <xi:include href="about.xml"/>- <xi:include href="history.xml"/>- <xi:include href="prerequisites.xml"/>- <xi:include href="structure.xml"/>--- a/docs/specifications/themes/themes.xsl Mon Aug 03 02:48:50 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/themes/Makefile Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,21 @@
+TRANSFORM_OPTS=--nonet --xinclude +spec.stamp: $(SOURCES) $(SHEET) + $(TRANSFORM) $(TRANSFORM_OPTS) -o $(OUTPUT) $(SHEET) $(BOOK) + rm -rf $(OUTPUT) spec.stamp --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/themes/about.xml Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,33 @@
+<?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>About</refentrytitle> + <refmiscinfo>About the Notification Theme Specification</refmiscinfo> + Notifications and themes go hand in hand when being displayed to + an end user. But with three different notification frameworks + being actively developed, why should there be a need for three + different themes for the same application? That is the main + question that this specification is going to attack, and present + a solution that all three projects: + <ulink url="http://www.guifications.org">Guifications</ulink>, + <ulink url="http://galago-project.org">Notification Daemon</ulink>, + and <ulink url="http://growl.info">Growl</ulink> can agree on and + By agreeing to this specification, it is by no means a contract to + only use or implement themes in this fashion, but to make a better + experience with the end users and theme developers. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/themes/history.xml Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,42 @@
+<?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>History</refentrytitle> + <refmiscinfo>Notification Themes History</refmiscinfo> + <title>History of Notifications Themes</title> + Each project has had unique experiences with their attempts to + implement themes. As such we feel it beneficial to discuss them + here to explain why we are looking for a specific format to adopt. + <title>Guifications</title> + Themes were initially introduced in Guifications 2.x to combat + a growing problem that Gary Kramlich saw; In Guifications 1.x + users had the ability to customize the background image and the + text seen in the notifications. This meant, that for someone + to have the same or similiar notifications as another, that + they would have to copy their settings manually. This was + unacceptable. Thus a theme format was created. + It was aparent around the time of Guifications 2.4 that the + theme format would not scale to quite what Gary wanted. + Unfortunately, due to the amount of 3rd party themes already + created, it was decided that the necessary changes would go + into Guifications 3 rather than a Guifications 2.x release. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/themes/prerequisites.xml Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,41 @@
+<?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>Prerequisites</refentrytitle> + <refmiscinfo>Prerequisites that need to be considered</refmiscinfo> + <title>Prerequisites</title> + Each notification engine/frame work has their own goals and + expectations of themes. As such, there are all stated here. + <title>Guifications</title> + Guifications is a bit more complicated than Notification + Daemon and Growl. Because of this, the expectations of the + Guifications developers, for what they want to see in this + specification are a bit more indepth. + <title>Notification Daemon</title> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/themes/structure.xml Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,28 @@
+<?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"> +<chapter id="structure"> + <title>Structure of a Notification</title> + Each notification engine/frame work has their own goals and + expectations of themes. As such, there are all stated here. + <sect1 id="attributes"> + <title>Attributes</title> + Each notification will have a summary/title that will give a + general synopsis of what the notification is for. --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/themes/themes.xml Tue Aug 11 02:18:06 2009 -0500
@@ -0,0 +1,14 @@
+<?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="notification_themes" xmlns:xi="http://www.w3.org/2003/XInclude"> + <title>Notification Theme Specification</title> + <releaseinfo>$Id$</releaseinfo> + <xi:include href="about.xml"/> + <xi:include href="history.xml"/> + <xi:include href="prerequisites.xml"/> + <xi:include href="structure.xml"/> --- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/docs/themes/themes.xsl Tue Aug 11 02:18:06 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"/>
