One of my Twitter friends retweeted a link to a post of the “Top 5 Coding Albums Of All Time” earlier (with his own comment that he’s more of an Op Ivy type of guy), and it got me thinking. What would my top 5 coding albums of all time look like? I’m not really sure how to answer that question (I’ve never been very good at creating “top 5” or “top 10” lists, because I am never able to shave things down to such a small number), but I do know that none of the five listed on that blog post would be on my list.
In an age where user feedback and interaction has become so popular, accessible forms have become that much more important. Many sites have already embraced making their forms accessible, and done a pretty good job of it, but inevitably some will still lack that little extra something – as small as an inappropriately named label through to no accessible features at all.
1. Using label tags
Labels should always be used and include the for attribute (e.g. <label for="name">). The value used should match the id of the input field that the label is being used for:
I honestly have no idea when this was announced, but Twitter will start disabling its “Basic Auth” on Aug. 16, 2010 (the system will be completely unavailable by Aug. 31). For Twitter users, this doesn’t really mean anything. However, for Web developers that use various interfaces and plug-ins to share information on Twitter, this is big.
The majority of API libraries and classes that were (and, as of this writing, still are) listed in the official Twitter API documentation will stop working. This change, as far as I can tell, will effect the way tweets are sent and the way tweets are received. Therefore, whether you’re trying to post tweets from an external source, or you’re simply trying to list your latest tweets, if the interface uses the old system of Basic Auth, it’s going to stop working on Aug. 31.
A few days ago, Paul Boag announced that he would not continue publishing the BoagWorld podcast past the beginning of next month. While I understand his reasoning, support his decision and am really looking forward to see what he produces in the future; I am also very sad to hear this news. The BoagWorld podcast has been an invaluable resource for me since I discovered it.
Moogo lets you create professional looking websites with a range of design and layout options for almost any type of content site. There are a wide range of options inside the Moogo portal and site creation is very quick and easy. It’s just three simple steps and if you can use Microsoft Word, you will be able to use Moogo.
The only thing you need to decide with Moogo is what features you want to use. Moogo offers you a Free Website with minimal options and features, something very basis if you are not ready for a full web presence. Then there are paid options ranging from $4.99/month to $14.99/month. I wont go into explaining the offerings for each of the paid plans, but I will explain the steps on how to setup the Personal Website plan:
Selecting a Layout
The first step is all about selecting the correct layout for your site. Moogo offers a variety of layouts from which you can select the one that best suits your needs. Assign the headers, the header is the top image on your page and you can select from a variety of categories, from Interests to Information Technology. You can preview your selections on the right side to see the picture of what the page looks like.
I am now attending a session on developing Web applications for the iPhone and iPod Touch. The presenter is Steve VanBrackle. Unfortunately, I have already discovered that this session is going to be completely dependent upon a Mac program called DashCode, for which there appears to be no Windows alternative. The interface for DashCode appears insanely easy to use, though.
To begin, VanBrackle simply created a new project. A working shell app was immediately created for him to edit and customize. All of the buttons, bars, etc. are automatically generated as part of the app.
He is now demonstrating how simple it is to click and drag information from a data store into the app. For the most part, it’s creating a JSON file to generate the data that’s being displayed in the application. Because of this format, it is easy to create the app a single time and then replace the data without having to redo everything.
At this point, he’s showing us how to add new buttons to the application, once again using click and drag interfaces. Once he places the button, a dialog appears presenting him with the choice of various event handlers that are available on the iPhone with buttons. By clicking one of the event handlers and typing the name of a function, a new, empty function is automatically created in the code window, allowing him to insert his custom code into the function.