Thus far, I have been spending cash like water. Most of this is due to things that either have to be paid (bills) or things that need to be fixed (my car). I am fortunate that I have some savings and thus it is not going to hurt me too much in the long run. Regardless, I’m not happy with the necessity of spending so much.
On the subject of spending, I really need to spend more time working out. Typically, I run about 15 minutes every night but as of late illness and lack of time have been preventing me from doing so.
Does anyone know of a OS X compatible dice roller that uses conventions found in Storyteller games (i.e. no summation of the die results)? Has anyone seen (or preferably played) the Exalted board game
War of the Throne?
XML Stuff:In my reading of
XML Primer Plus, I’ve come to some “conclusions” (subject to revision as I learn more). XML name spaces, can/are used to combine elements from different XML documents. This is particularly useful if you have to reuse elements (aka. <charm />).
For instance:
<data xmlns=”http://anathema.sourceforge.net/charms”
xmlns:srcy=”http://anathema.sourceforge.net/sorcery”
xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xsi:schemaLocation=
“http://anathema.sourceforge.net/charms ../charms.xsd
http://anathema.sourceforge.net/sorcery ../sorcery.xsd”>
<charm>
<id>solar.shadowstrike</id>
<duration>instant</duration>
</charm>
<srcy:sorcery>
<srcy:id>solar.celerityoftherisingsun</srcy:id>
<srcy:target>one</srcy:target>
</srcy:sorcery>
</data>
XML schema’s are fabulously complex and thus incredibly useful. You can make groups of various things: attributes, elements, value lists, etc. You can specify in much greater detail what contents are valid. Since it is hierarchical based, it deals better with repeated elements (aka. <charm />) that have different children or attributes.
You can combine XML Schema’s with name spaces to validate a document against two different schema’s. Which is particularly useful in the above example code. Sorcery has only 3 elements vs the minimum of 5 for most Charms.
I’ve also learned some interesting things about XSL. Apparently, there is an <xsl:transform xmlns:xsl=http://www.w3.org/1999/XSL/Tra
nsform" version="1.0" /> element. I didn’t realize that such an element existed, in part because none of my example documents used it, but according to the author of my book, it is being used more often now.
It also gives me a way to tinkering with the “Transformation” aspect of XSL. I would need to get a software called
Xalan which would allow me to utilize this. All I need to do is type in (assuming I can get it “installed” correctly):
java org.apache.xalan.xslt.Process -IN (Some XML Document) -XSL (Some XSL Document) -OUT (Some Document)
OR
java -jar path/to/xalan.jar -IN (SOME XML DOCUMENT) -XSL (SOME XSL DOCUMENT) -OUT (SOME DOCUMENT)
It would make mass conversion of XML documents relatively easy, assuming you didn’t have another way of doing the same thing.
Aside:Now to pickup my car and spend $160 US.
PS. Learning is always good but being able use that knowledge is better. Yes, I’m being enigmatic but that’s my prerogative.