From 2c9cb0784184346917f9ad509f9b2c4056b60167 Mon Sep 17 00:00:00 2001 From: rcoh Date: Wed, 16 Feb 2011 20:07:15 -0500 Subject: remove email address. --- behaviors/Flasher.py | 2 +- config/FireflyDemo.xml | 2 +- docs/XmlConfiguration.tex | 4 +++- 3 files changed, 5 insertions(+), 3 deletions(-) diff --git a/behaviors/Flasher.py b/behaviors/Flasher.py index 1d79d41..395d898 100644 --- a/behaviors/Flasher.py +++ b/behaviors/Flasher.py @@ -4,7 +4,7 @@ import util.ColorOps as colorops import pdb class Flasher(Behavior): """Implements a pulsing/flashing behavior. - Jim Salem: jsalem@gmail.com + Jim Salem Args: Factor - The speed of flashing. Must be b/w 0 and 1. Default is .95 diff --git a/config/FireflyDemo.xml b/config/FireflyDemo.xml index de639d9..06ae7ba 100644 --- a/config/FireflyDemo.xml +++ b/config/FireflyDemo.xml @@ -1,6 +1,6 @@ - + diff --git a/docs/XmlConfiguration.tex b/docs/XmlConfiguration.tex index a1cce8f..0ccd08d 100644 --- a/docs/XmlConfiguration.tex +++ b/docs/XmlConfiguration.tex @@ -17,7 +17,9 @@ As you will see, however, XML in SmootLight goes beyond simple configuration. XML in SmootLight allows us to declare a LightSystem (an inherently non-declarative thing) in the same way you might write a webpage in HTML. We will refer to the XML system here-on-in as - `SmootConf'. Without any further ado, lets start looking at + `SmootConf'. \textbf{The fastest way to get familiar with SmootConf is simply to look at + the XML files in the configuration file. However, if you want a more structured approach to + its feature and sublties this document should do the job.} Without any further ado, lets start looking at how this all works. \section{Declaring a class in SmootConf} The most common thing done is SmootConf is declaring a class -- Class declaration code will -- cgit v1.2.3