Welcome to the final blog post on delaying Edge Animate animations. I'm saying final just because I can't believe how such a simple thing has turned into so many different blog posts, so many different variations, and so many different fun diversions. Most likely because I said this will be the final post, someone will discover some other interesting opportunity and I'll have to write a part 5. But hey - that's the fun part about being a developer, right? Before we start though, please be sure you've read the earlier posts. I'll link to them at the bottom.
A few weeks ago a reader asked if I had ever designed a quiz for jQuery Mobile. While I had not, I spent some time thinking about how a quiz could be designed as well as how a generic library could help automate it. I've built a demo I'd like to share with folks. It is definitely "First Draft" (but hey, it lints!) so feel free to tear it apart and suggest improvements.
I'm currently working on an article that discusses various third party services that can help flesh out a static web site. While researching that article, I got to thinking about contact forms and how (or if) I could use Parse to power them. Parse is built for ad hoc data storage of - well - anything. I wouldn't typically think of contact forms as being something I'd want to save, but the more I thought about it, the more I thought that in some organizations this could be a powerful feature. You can track communication over time as well as use the email addresses as a list to contact in the future. There are probably multiple ways of doing this, but here is what I came up with.
Earlier this week I blogged about the relaunch of Ripple, a great tool for building your mobile applications with Chrome. One of the issues with the new version of Ripple is that when you edit your code, you have to run "cordova prepare" to copy the assets into your platform before you can view it in the browser.
Obviously you can ask me as well (grin), and in fact, someone on the group already asked for a few small examples that I thought I'd share here. Nothing too exciting, but here we go.
Just a quick note - and followup to my review of NodeSchool. Yesterday I discovered ExpressWorks. ExpressWorks uses the open source framework behind NodeSchool to create a similar experience for ExpressJS. I've blogged (and written) about ExpressJS before. Essentially - this is the framework that got me to give Node.js a try and really "sold" me on Node in general.
So, as a rule, I refuse to answer questions about ColdFusion UI tags. I definitely blogged about them in the past, but like others, I've come to realize that they cause more problems then they solve. To quote the great one...
Just a quick tip here (and thanks to multiple folks on Twitter for guiding me to this) that I hope is helpful. I'm working on a web page that is pretty complex and has a series of scripts that are being loaded that I have no (direct) control over. My task was rather simple - given a link of a certain class - make note of the click event and do something before allowing the link to carry on as normal. This worked fine until this week. This is how I diagnosed the issue.