A brand-new project and my first (here) in Node. It’s a simple-to-use converter to make HTML out of XML docs. I’m hoping to add other output formats later on.
Ever wanted to load a podcast (or several) onto your web site, but didn’t have the resources to make a proxy to get around cross-domain scripting issues? Worry no more! PodRadio.js is here.
I had a problem that I got to solve using something I rarely (if ever) use: jQuery.inArray(). While working on a new tool for doing Improv practice, I came across an interesting problem that might be worth sharing.
Just add it (and jQuery) to your page, then define which HTML elements you want to make the snap points. I love simple-to-use code, don’t you?
I’ll add onto it later as new ideas pop into my head. Right now, it’s using a timeout to account for the fact that there’s no scroll-end event in the DOM or jQuery. I’m not a huge fan of timeouts, but in this case it seems to work. I’d like something more elegant going forward.
Getting started building an API can be tough if all you’re looking at are big, monstrous (but useful) APIs. To combat this, I’ve built a really simple API to redirect users based on the hash in their URL. It initializes, take external data, and returns a response block.
You all remember parts of speech, right? Nouns, verbs, adjectives, pronouns, and so on from elementary school, right?
Well, some of you do.
In my last installment, I covered loading external JSON files into your code. That works great, if you have reasonable control over the data format.
If you’re dealing with a vendor or open data source, you may not have the control you want to make a JSONP call (or the data is in XML instead of JSON). There’s a way around this by using a proxy.
- Code is easier to read for the developer and those that follow.
- Structure allows for future additions and creates a pattern for all future work.
- Code is testable