While converting ASP.NET Webforms to be more clienty using HTML 5, Knockout, and jQuery, I came across a problem.
I read that you learn more from a poor example than from a correct one. I don't believe this but that means my site will be a success.
Matt Blair
My jQuery bug was already documented. :(
I finished up the Nike+ data importer for www.runningahead.com. You can check out the code for the importer at this Github repository:
I love to find bugs in good software! Came across a little jQuery UI bug today. It’s for one browser, but it always excited to be able to create an easy-to-replicate bug. The bug is small - it deals with the buttonset() method.
Is there anything better in life than finding a better way to do something? An easier commute, a better night’s sleep, a tastier cake recipe? In starting the Nike+ importer for www.runningahead.com, I knew I was going to have to deal with a bit of XML. Which used to mean XPath. Not so much anymore. LINQ to XML, you rock my world. It turns XML like this…
I’m a fan of the website www.runningahead.com. I use it to track all my sporting life activities. The primary reason I use this site, instead of one of the hundreds like it, is that you can track anything - yoga, rowing, running, P-90x, underwater hockey, tiddlywinks, whatever. Throw in some customizable reporting and some great hardware integration, and it’s free, and you’ve got a winner.