Mozilla Developer Center is hard to navigate or search to find useful information, which is too bad, because there are some gems hidden away in it. One of the ones I come back to again and again is the Core Javascript Reference 1.5. Javascript 1.5 is out of date now, but in this case it just means this reference is useful across more browsers.
I have become a major fan of jQuery, so the docs for it have found a place on my bookmark bar as well.
A key site for looking up web standards info is W3Schools, and their Javascript section is sometimes helpful, although their HTML DOM section is even better, especially for the semi-standard DOM Level 0 stuff like window and location.
For questions about the DOM, I still go back to the W3C DOM Spec, especially Appendix H, which is the ECMAScript (Javascript) Binding, or API.
Finally, I sometimes find that the Microsoft documentation for IE is helpful. They often reorganize their site, and their search isn’t very helpful, so the best way I’ve found to find information is to use google search with the term site:msdn.microsoft.com in addition to your search term(s). I don’t know how anyone at Microsoft finds things on their own site, but I expect they end up using Google too.
Those are the essential references I use. None of them are particularly helpful for learning Javascript in the first place, or for developing a good style and using more advanced techniques, or taking advantage of browser specific features. If there is interest, I can write about those another time.
]]>Two of my back-burner projects, better blue-screening, and easy lightsabre effects, have been done by others recently. Inspired by the same BoingBoing piece on rotoscoping your own lightsabres as I was, but Naked Software actually sat down and wrote the code. It’s pretty slick, too. For blue-screen effects (and many more), check out Sam Kass’ Quartz Composer Compositions. Very neat stuff, Tiger-only though [Update: now Leopard]. Some of the compositions require a newer system with a higher-end video card than my three-year-old PowerBook.
But to be honest, the real point of this post is not to tease with coming attractions, but to point out my first paid publication. My friend David Mertz asked me to collaborate with him on his XML Matters column for IBM developerWorks, and my first column went live last Friday: Beyond the DOM.
I’ve wanted to be a writer for as long as I can remember, with poetry notebooks and 200 pages of a novel gathering dust on my bookshelves, so finally getting around to finishing something and having it published leaves me pleased as punch. And more will be forthcoming.
]]>In the last episode we learned how to initialize many of the DOMs and DOM-like tools for Python from an XML document. Today we’re going to see how to convert these back to XML from the DOM. So fasten your seatbelts and let’s go.
import domParse
from xml.dom.ext.c14n import Canonicalize
def stringMinidom(filename):
return Canonicalize(domParse.parseMinidom(filename))
def string4Dom(filename):
return Canonicalize(domParse.parse4Dom(filename))
def stringDomlette(filename):
return Canonicalize(domParse.parseDomlette(filename))
def stringLibXml(filename):
# pretty-printed, which may not be what you want,
# depending on the XML in question
return domParse.parseLibXml(filename).serialize(encoding='utf-8', format=True)
# 4DOM c14n breaks because libXML doesn't give you a DOM
# return Canonicalize(domParse.parseLibXml(filename))
def stringPxDom(filename):
import pxdom
serializer = pxdom.LSSerializer()
return serializer.writeToString(domParse.parsePxDom(filename))
#return Canonicalize(domParse.parsePxDom(filename))
def main(filename):
print '4DOM:', string4Dom(filename)
print 'Domlette:', stringDomlette(filename)
print 'MiniDom:', stringMinidom(filename)
print 'LibXml:', stringLibXml(filename)
print 'PxDom:', stringPxDom(filename)
if __name__ == '__main__': main(domParse.small_filename)
As you can see, there’s not much to it. This codes does require that you’ve installed the PyXML package, but if you’re serious about XML in Python, that will already be the case. In our next outing we can explore some of the less DOM-like, but more Pythonic ways to play with XML.
PyXML: http://pyxml.sourceforge.net/
4Suite: http://4suite.org/index.xhtml
libxml: http://www.xmlsoft.org/ (instructions for the python bindings are linked from this page)
pxdom: http://www.doxdesk.com/software/py/pxdom.html
You may now return your trays to their upright positions.
]]># Examples for reading in various DOMs from an XML file
# MiniDOM
def parseMinidom(filename):
try:
from xml.dom.minidom import parse
doc = parse(filename)
return doc
except Exception, e:
return 'parseMinidom() failed with exception %s' % e
# 4DOM
def parse4Dom(filename):
try:
from xml.dom.ext.reader.Sax2 import Reader
f = file(filename)
reader = Reader(validate=0, keepAllWs=0, catName=None)
doc = reader.fromStream(f) # slow!
f.close()
return doc
except Exception, e:
return 'parse4Dom() failed with exception %s' % e
# Domlette
def parseDomlette(filename):
try:
from Ft.Xml.Domlette import NonvalidatingReader as reader
f = file(filename)
uri = 'file:///%s' % filename # suppress warning
doc = reader.parseStream(f, uri)
f.close()
return doc
except Exception, e:
return 'parseDomlette() failed with exception %s' % e
# libXml
def parseLibXml(filename):
try:
import libxml2
f = file(filename)
data = f.read()
f.close()
doc = libxml2.parseDoc(data)
return doc
except Exception, e:
return 'parseLibXml() failed with exception %s' % e
# pxDom
def parsePxDom(filename):
try:
import pxdom
doc = pxdom.parse(filename)
return doc
except Exception, e:
return 'parsePxDom() failed with exception %s' % e
def main():
import sys
filename = sys.argv[1]
print '4DOM:', parse4Dom(filename)
print 'Domlette:', parseDomlette(filename)
print 'MiniDom:', parseMinidom(filename)
print 'LibXml:', parseLibXml(filename)
print 'PxDom:', parsePxDom(filename)
if __name__ == '__main__': main()]]>