Elliotte Rusty Harold roundly Read more
If you’re working with XML, as I currently am, XSLT can sometimes be a godsend. Something that would take ages to do in a structured, procedural way can be reduced to two or three lines of functional XSL code.
So it was with a growing sense of consternation that I noticed that adding XML namespaces to the original document seemed to break XSL’s ability to recognise elements! Consider:
<elem/>
A number of posts are currently in stasis waiting for me to actually finish them, but I thought it was worth mentioning the selection of my most recent Flickr photos that now graces my homepage. While the rest of that page awaits serious styling and content work, I’ve dilly-dallied by creating this bit of eye-candy.
After a bit of a struggle I’ve managed to get wireless networking at home. Unfortunately, my first attempts to test the connectivity to the rest of the world coincided with the power outages at Telehouse, a “bullet-proof” ISP that too many people rely on, including ADSL services, the BBC website, Nominet, some DNS servers….
Following my recent success with putting a Flickr feed on my website’s front page is the conversion of this to an all-purpose feed reporter, where RSS/Atom flavour and feed specifics are dealt with by Javascript associative arrays of functions, keyed on both variables respectively.
Now I know the title sounds presumptuous, but there’s a certain methodology I’ve settled into that seems to work really well for encouraging Javascript that’s legible and safe. I thought I’d share it with anyone that doesn’t consider themselves a JS playa, in case it’s of some use to you too.
Firefox’s implementation of Javascript is quite forgiving: often a little too forgiving, when it ought to be strict about issues that could pose a security risk. Indeed, Firefox’s silent “the programmer meant this” in the instance I’ve just been tackling was only revealed by the IE error:
No such interface supported
What happens when nobody will take responsibility for a standard that the web relies on?
Sick and tired of getting a million hits, all to the same page, which more often than not hasn’t been updated in the mean time? Want to reduce your bandwidth and server-time loads without necessarily impairing your visitors’ experience of your site?
Drupal, along with Plone and dotnetnuke, beat some monumentally big playas to the first awards of the OpenID bounty. This is awarded to projects which implement a number of requirements which, together, constitute agreed OpenID functionality.