61 items tagged “mark-pilgrim”
2005
Mark Pilgrim goes both ways. Fighting greasemonkey scripts.
2004
The myth of RSS compatibility [dive into mark]. Sometimes I think Mark’s raison d etre is to upset Dave Winer
2003
Blogmarks
This entry was going to be another list of links, together with a note about how much I really needed to set up a separate link blog. Then I realised that it would make more sense just to set one up so that’s exactly what I’ve done. I still need to implement the archive but it’s getting dark so I’m posting this and heading home.
[... 211 words]Dive Into Python reborn
Sweet. Mark Pilgrim is working on Dive Into Python again, funded by a dead tree publisher for publication in 2004 (hopefully). The free version will stay available as well. I’ve always preferred reading paper to reading a screen so I’m definitely down for a copy.
[... 135 words]Sitting nervously on the fence
Today’s hot topic is the Winer Watcher, Mark Pilgrim’s new tool that tracks and highlights edits made to Dave Winer’s Scripting News. The blogosphere is pretty much evenly split on this: some people think it is a blatant attack on Dave Winer, tantamount o blogger bullying, while others see it as a neat technical solution to a very real problem.
[... 1,146 words]Python power
Sam Ruby’s ultra-simple 3-paned aggregator is a great example of the power of high level scripting languages. Using the wxPython cross-platform GUI toolkit and Mark Pilgrim’s ultra-liberal RSS Parser it provides a full application in a mere 107 lines of (highly readable and maintainable) code.
[... 127 words]Dynamic Python class methods
Dynamically extending APIs: Mark Pilgrim demonstrates how Python’s “new” module can be used to dynamically add new methods to existing classes at run time, and shows how this can be used to increase productivity when parsing XML. I’ve long been impressed with Python’s ability to add new methods to an object at runtime just by assigning a function reference to an object property but I had no idea it was possible to do this with classes as well. If you liked that tip, Dive Into Python has in depth explanations of more obscure Python features than you can shake a stick at.
Safari conditional comments
The current extended discussion over whether or not Safari should have some kind of specific CSS blocking technique built in (sparked off by Mark Pilgrim) reminds me of a relatively unpublicised feature of Internet Explorer called conditional comments. These specially crafted HTML comments allow web authors to specifically hide code from versions of IE, or alternatively to hide code from any browsers that are not a specified version of IE. Here’s how they work:
[... 198 words]2002
Mark goes XFML
Mark Pilgrim has discovered XFML. He provides an excellent description of the standard, but fails to mention XFML’s most powerful ability; sharing metadata. Here’s how it works:
[... 225 words]Googlebad
Mark Pilgrim explains why Google’s latest update tweaks (mentioned yesterday) are a lot less harmless than they first appeared.
Pingback coverage
The Pingback 1.0 specification is getting some serious attention. Mark Pilgrim and Dave Winer have linked to it. Ben Trott (co-author of Moveable Type and creator of TrackBack, the system that inspired Pingback) has objected to Hixie’s suggestion that Pingback is more transparent than TrackBack, claiming that TrackBack could be made just as transparent by the right blog tools. Ben blogged some further thoughts which lead to the following comment by Phil Ringnalda:
[... 278 words]RSS2 modules
It seems RSS 2.0 has the capability to support modules (I was under the false impression that this ability was restricted to RDF modules in the rival RSS 1.0 specification). Following a post by Mark Pilgrim on B-linking (the blogging equivalent of a B-movie) Dave Winer has released a draft of blogChannel, the first ever RSS 2.0 module.
Python RSS locator
Mark Pilgrim has written an ultra-liberal RSS locator (in Python, naturally). I guess he had to scratch an itch. The amount of work it puts in to locating an RSS feed for a site is astonishing, especially when you consider how short the actual code is.
Fun with Amazon
There’s plenty of activity surrounding Amazon web services today. My limited demo barely scratches the surface of the possibilities—people are already experimenting with Amazon’s similarity search and Mark Pilgrim has released PyAmazon, a Python wrapper for the Amazon API. I’ve started listing alternative implementations on the PHP Amazon Search page, and I’ll be sure to blog the more innovative examples as and when I find them.
Accessible headers
Mark’s latest accessibility tip concerns header tags (<h1> through <h6>). Mark explains that using headers in the right order helps screen readers to interpret the structure of your pages, and shows how to use CSS to effectively style headers. Mark once again demonstrates the comment hack as a way of bringing Netscape 4 in line with other browsers, a technique that has been criticised by the More Like This Weblog as unnecessary encouragement for NS4 users. Incidentally, Johannes Koch has an excellent summary of CSS hiding techniques.
Accessible fonts
Mark has out-done himself today with his long awaited coverage of relative font sizes. This is a notoriously tough topic (thanks to a whole bunch of strange CSS bugs and browser differences) but Mark carefully and comprehensively explains the various work arounds and CSS hacks needed to get the right effect with maximum accessibility.
Jonathan on longdesc
Jonathan has insider knowledge that Mark will not be covering the longdesc attribute in his accessibility series. This it not because longdesc is not a useful accessibility tool, but simply because it does not fit the “fire and forget” nature of Mark’s series. Jonathan’s post discusses longdesc and the difficulties involved in adequately describing an image.
Alt all the way
Mark says that today is the most important day of his whole accessibility series, and who are we to argue? The topic is the alt attribute for images, and the message is simple: Every image should have one, even if the image is there purely as layout decoration (in which case an empty attribute should be used). Surprisingly Mark does not give advice on chosing text for the attribute but he does provide an excellent further reading list, which includes Hixie’s superb Mini FAQ About The Alternate Text Of Images.
Final table tip
A final table tip from Mark: Providing a summary for tables. Mark explains the summary attribute which should be attached to every <table> tag to summarise the purpose of the table. Tables used for layout should include an empty summary attribute to show they are layout tables (in a similar way to empty alt tags for layout images). The summary attribute is only used by text to speech browsers, so I’m slightly confused as to why it should be included for layout tables—surely if the attribute is empty a speech browser will skip tstraight over it as if it wasn’t there?
Accessible tables
Mark has been educating us on the accessible way of marking up tables, with particular reference to calendar tables on blogs. My blog doesn’t have a calendar (yet, I’m considering adding one) but Mark’s articles have brought up some interesting things that I was previously unaware of. Giving your calendar a real caption explains the <caption> tag, which can provide a useful (and easily styled) caption for any table. Using real table headers explains how <th> tags are interpreted by speech browsers and shows how they can be used in conjunction with the abbr attribute to create more accessible table columns.
More tips from Mark
Time to catch up on Mark Pilgrim’s accessibility tips. Four have been added since I last checked, so I’ll go through them in turn.
Additional navigational links
Today’s accessibility tip: Providing additional navigation aids. Mark explains the concept of “relative” links using the <link> tag, which can be used to provide shortcuts to the next and previous page in a sequence as well as links to a site’s homepage. He also provides instructions for implementing them in Moveable Type, and asks for suggestions as to how it could be done in Radio. These links are not rendered in the actual body of a page but can be used by many browsers to provide additional navigation aids. My blog has these already but only as shortcuts to my categories and a link back to the home page—I haven’t yet implemented them for next/previous buttons while browsing the archives (which is arguably their most useful ability). Time to get hacking...
Day 8: page titles
Day 8: Constructing meaningful page titles—the accessibility tips are flying thick and fast now. I’ve always been conscientious of my page titles (after all, they’re all you get when when you use your browser’s history feature) but it seems I was not quite conscientious enough. My titles now all carry a reference to the name of the blog in addition to a description of the page.
Mark replies
Mark mailed me in response to my query about limiting his accessibility series to weblogs rather than expanding it to cover general sites:
[... 176 words]Day 6: Doctypes
Mark Pilgrim starts his series of weblog accessibility tips today with tutorial on adding a doctype to a blog.
Jonathan on Mark
Jonathan has meta-blogged (I think that’s the term) responses to Mark Pilgrim’s accessiblity series. He replies to my query about the wisdom of limiting the series to bloggers rather than expanding it to cover as much as possible:
[... 166 words]Mark explains all
Over at diveintomark Mark Pilgrim has explained the aims of his Accessibility series:
[... 208 words]