aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorGravatar rcoh <rcoh@mit.edu>2011-02-16 20:07:15 -0500
committerGravatar rcoh <rcoh@mit.edu>2011-02-16 20:07:15 -0500
commit2c9cb0784184346917f9ad509f9b2c4056b60167 (patch)
treebcc45222a53240f3aaadab5e70db5f2ec23b813e /docs
parent14a83772c12570e51387a316a7e5f2e4d9d46dd0 (diff)
remove email address.
Diffstat (limited to 'docs')
-rw-r--r--docs/XmlConfiguration.tex4
1 files changed, 3 insertions, 1 deletions
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