Image-Free Progress Bar using MooTools and Canvas
As part of my ongoing experiments with
Custom modal windows using canvas and MooTools
I’ve built a simple modal window class named Modal using MooTools. This class combines a dynamic canvas drawing API (my Rectangle class) with dynamic DOM element generation to create on-demand modal windows using no external images. My goal was to make this about as easy to use as a normal JavaScript alert, prompt or confirm window.
Hawaiian diacriticals
This brings me to one of my pet peeves and the purpose of this post: misuse of the backtick (`) character. Many of the afore-mentioned well-intentioned folks mistakenly use a backtick to represent an ‘okina, and it drives me absolutely bonkers.
Fun with canvas and MooTools: a Rectangle class
Recently at work I realized I needed a good modal window that was more extensible than JavaScript’s built-in confirm and prompt windows. MochaUI looked like a handy way to get slick modal windows into my project, but I soon realized that MochaUI is designed to do much, much more than I need, and therefore is (for my purposes) bloated. So, in typical DIY fashion here at pipwerks, I decided to borrow a page from Greg’s book and make my own MochaUI-inspired modal window using the canvas element, CSS, HTML, and MooTools. After evaluating what I’d need for my little modal window, I whipped up a MooTools-based JavaScript class that produces canvas rectangles in the blink of an eye.
Obfuscating email addresses, revisited
A while back, I posted my method for defeating spambots that harvest email addresses. This post is an update to that original method. It explores cleaner, less obtrusive code approaches and more accessible/usable HTML markup.
Constructive criticism for the new whitehouse.gov
The new whitehouse.gov site has received a lot of press since its unveiling a few days ago. Many have rightly given it kudos for bringing a modern sense of design and “Web 2.0”-style social practices to the White House. I agree that the new site is a big improvement, but upon looking under the hood, there are a number of things I’d have done differently. Here’s a quick-hit list (not comprehensive at all)…
Adobe eLearning Suite and Captivate 4 released
Adobe has officially announced Captivate 4 and the Adobe eLearning Suite. My first thought upon finding out about the eLearning Suite a few months ago: “Why should I buy the eLearning Suite if since I already have CS3/CS4? The only real difference seems to be the inclusion of Captivate, which I can get separately, and Presenter, which I probably won’t even use.” The answer is…
SCORM resources
I recently emailed a shortlist of good SCORM development resources to a colleague, and figured I should probably post a list here, too. This is a quickie list, and I’m sure I’m leaving someone out. If you know of any resources I’ve missed, please add a link in the comments. This list is presented in no particular order.
Fixed-width layouts
While working on a recent web project at work, I wondered if I should go for a fixed-width layout or stick with my preference for fluid layouts. Fixed-width layouts are certainly easier to manage, but they just feel so… rigid. With the boom in larger monitors, I also wondered if fluid sites start presenting a problem due to being too wide. I decided to check around the web to see what others are doing.
SCORM 2.0: high-level solutions or low-level tools?
Matt Wilcox posted an interesting argument about the CSS3 standard; I think the central points of the argument can be applied to SCORM and where we’re potentially headed with SCORM 2.0.