Hi, I like Apples

If you’re following my Twitter feed, you probably know that I’ve been ecstatic about a fairly new content management system for Digital Humanists creating digital archives. The web software is called Omeka, and it’s out of the Center for Digital Humanities at George Mason University in Virginia.

Omeka has a rich API (application programming interface) that lets developers and creatives alike create awesome plugins and additional content that flows right along side of the CMS. I have been actively developing Omeka plugins for the past academic year at my university in hopes of making Omeka more accessible to visually impaired people accessing the Omeka archives. The development was sponsored by two grant-related projects that I’m involved with. The first project is LookListenTouch.org which I worked for Fall 2009, and BrailleSC.org that I’m currently working on.

People who are visually impaired generally access websites using screen reading software like JAWS or Apple’s screen reader VoiceOver. This software reads aloud what’s on the screen, but screen readers don’t work well with certain web content, namely Adobe Flash, JavaScript and Java applets. Fortunately, Omeka’s front-end doesn’t rely on any of the technologies, making it pretty accessible out-of-the-box. However, the accessibility plugins I’ve developed expand on the universal design model, making Omeka even more accessible.

The first of the plugins is an Access Keys plugin. This plugin lets the administrator assign Access Keys, which are one-character keyboard shortcuts, to basic Omeka functionality, such as go to the home page, browse by items, browse by collections, skip to next item, skip to previous item, and skip directly to the content. Normally people accessing websites with a screen reader need to listen to a list of menu items each and every time they listen to a page being read, but with the Access Keys model, they can memorize a set of keys, then jump to any page they wish to go to. For example, if you wanted to go to the search page, you can press Control + S and go directly to the search page in Omeka.

Access Keys can provide a ton of usability for user accessing a particular website, making navigation easier than ever before. The thing is, Access Keys have been around since around 1999 — why haven’t they been used before? Well, I’d suggest that’s partially because different web browsers use different modifier keys (i.e. pressing control, command, or shift before pressing the access key in order to activate a link). That’s why BrailleSC.org and LookListenTouch.org is advocating the standardization of modifier keys across different browsers, operating systems, and versions of browsers. This would make life easier for users and developers alike.

Continuing on the idea of Access Keys, I’ve also developed a custom Access Keys plugin that will allow an Omeka administrator to specify up-to 10 URLs and Access Keys that will be available from any page inside of Omeka. For example, you could go to Google.com by pressing Control + G.

Of course, Access Keys are limited to the number of letters and numbers available on the keyboard, so that’s 26 + 10 = 36 available keys. Symbols are not available for assigning Access Keys, and remember that if the shortcut assigned is also a shortcut for the web browser (i.e. in Internet Explorer Control + B is for bookmarking pages), then the assignment will overwrite the browser functionality.

The Last plugin that I’ve completed is one called “TextZoom” that, like its name implies, lets the user enlarge the text on the page. When the admin enables this plugin, they also can specify Access Keys for the enlargement functions. There is five levels of enlargement: default, small, medium, large, and extra large. When a user selects any of the enlargement levels, the settings are automatically remembered for 30-days using a cookie, so when they visit the site again, the text will automatically be enlarged for them. The user can then press the default option to go back to the default site and remove the cookie from their browser.

There are other plugins that I’m working on, including a Google Analytics plugin that will let an administrator look at current website tracking information right from within the admin pages.

Where Can You Get The Plugins?
I have the three plugins mention in detail above available for download at BrailleSC.org/development. I also have the source listed on my own development wiki at CoryBohon.com/development. The plugins are completely open source, so if you wish to take the source code an improve it you can under the terms of the included GNU public license.

If you have any questions about the plugins, you can email me directly at cory [at] corybohon [dot] com or cory [at] braillesc [dot] org.

If you live on planet earth, then you know Apple announced the release of its newest invention, the iPad this week. A lot of people have been speculating about this device, wondering what market it’s for and what all it might be capable of. Many people have mixed feelings about whether or not they will purchase one, also. In this post, I want to let you know why I chose to get one and also what the iPad means to the developer community.

The iPad has been compared to a “giant iPhone or iPod touch,” but I simply don’t think that’s what this device is. Sure, the device is running iPhone OS 3.2, but the OS and software has so many more possibilities than the iPhone or iPod touch. I’d imagine Apple chose this operating system over Mac OS X because it’s extremely touch-friendly and because probably half the population of the world has seen and/or used the iPhone OS. If people already know how to use a piece of software or hardware, the chances they’ll purchase and enjoy it is more likely because they can relate to it.

But the OS is just one small part of the device. The third-party software that can be written for the device is generally about the same as the software that can be written for Mac OS X. There’s a few differences, but for the most part high-quality software can be written for this device. Take Apple’s own iWork for the iPad. They are taking a piece of software from the Mac that’s pretty hefty and porting it to a device that supports Multi-touch gestures for manipulating text, images, slides, and spreadsheets. To me, that’s the amazing part of this device. My hope is that developers take heed to the wonderful iPad SDK Apple has released to develop desktop-class applications that can take full advantage to the Apple designed processor, and touch screen.

People have been badgering the device because there’s no Adobe Flash playback, but I’m not so sure that’s a problem. Flash has been around for a long time and has been adopted by a lot of websites, but that doesn’t mean it’s the best use of the technology. Microsoft has also came out with their own sort of technology called Silverlight. These technologies, however, often take up lots of memory and CPU. And for what? Video playback? Games? All of these tasks can already be done with the iPad if developers would take a look at creating apps. Not a fan of apps? Apple is simply addressing the future. Because of the iPhone and lack of flash support, Apple has forced developers to take a look at other technologies to accomplish these simplistic tasks. Adobe is just angry because Apple is slowly taking away their market, but the truth is that flash is on its way out (or at least should be). Advanced CSS and HTML techniques give web developers the ability to add video playback and game design right on a webpage without using the resource hogging flash that’s common today. YouTube has already adopted many of these techniques and it’s simply beautiful to see in action.

Too many people have compared the iPad to the Amazon Kindle and various netbooks. The iPad is in a completely different class than those devices, and the iPad will probably take a good bit of market share from those and other devices like it. Apple has created a device that can do eBooks (or iBooks as they’re calling them), it can do HD video from either iTunes or YouTube (another game changer for parents who despise portable DVD players and the ever-so-scratchable discs), and it can do productivity with the iWork suite (I’d imagine it’s only time before Microsoft joins in, please?). Sure it doesn’t have an e-Ink display, but so what? Many people read and have no problems reading from an LCD monitor everyday. Plus, you don’t need a book light like you need to have to read in the dark with e-Ink devices. Plus, this device is in full color and has a 9.7″ screen that will be amazing for displaying textbooks in PDF or ePub format.

Basically, I’m just a little disappointed that people are already bashing this device when it (1) hasn’t been released yet, and (2) hasn’t been used by anyone except people at the media event last week. The iPad has a lot of potential if only people would look at that. This device is truly a game changer. The Amazon Kindle DX is only a few dollars less than the basic iPad that costs $499, a few dollars separates these two devices that are completely different. Except, the iPad can do all that the Kindle has to offer. The Kindle, however, cannot touch what the iPad has to offer.

Want a game that gives you loads of fun to play when you just have a few minutes to spend? Well, Ceville for iPhone has you covered. This fun action arcade game lets you blast your way through three different levels: the dungeon, the oasis, and the graveyard, where you will fight off enemies with tomatoes ranging from zombies to flying faeries. Choose between two awesome characters: Ceville or Lilly and play away to your hearts content. Tilt your iPhone to pan around the different scenes as you toss tomatoes at enemies. Ceville is great fun at a great price.

Ceville is available from the iTunes App Store for just $1.99-U.S. You can also get a free lite version from here.

‘Twas the night before Macmas, when all through the house
Not a harddrive was whirring, not even a Mighty Mouse.
The iPods were placed on their docks with care,
In the hopes that St. Steve would soon be there.

The Apple fans were impatiently waiting all snug in their beds,
While visions of tablet-Macs danced in their little heads.

When up on the roof arose such a clatter,
I sprang from my bed to see what was a matter.
Away from Microsoft Windows I failed like Adobe Flash,
Tore open the Aperture and threw up the sash.

When, what to my wondering eyes should appear,
But Steve Jobs and eight tiny iDeer.

“Now Phil! now, Scott! now, Johnny and Tim!
On, Bertrand! On, Peter! On Mark and Ron!
Top the top of the porch! To the top of the wall!
Now flick away, Flick away! Flick away all!”

And then, in a twinkling, I heard on the roof
The prancing, the pawing of each little iHoof.
As I drew in my head, and was turning around,
Down the chimney St. Steve came with a bound.

He was dressed all in Snow Leopard fur, from his head to his Nike Plus foot,
And his turtleneck and blue jeans were all tarnished with soot.
A bundle of Apple goodies he had flung on his back,
And he looked like a salesperson, just opening his Apple bag.

He sprang to his iSleigh, to his executive team gave a whistle,
And away they all zoomed like the Mac Pro’s processor.
But I heard him exclaim, ‘ere he drove out of iSight,
“Happy Macmas to all, and to all an Apple-night!”

The other week I decided to order “The Wikipedia Revolution” by Andrew Lih after I heard Leo Laporte talking about it in his speech on journalism in today’s world. After reading the book, I would have to agree that this book is an awesome resource for anyone looking to get more information on Wikipedia.

Even though much of the book is focused on the online wiki-based encyclopedia, Lih gives your brain a stroll down memory lane by telling you the history of the wiki software and how it came to be. There’s also discussions about the GNU licensing and the idea of a “copyleft.”

One of my favorite chapters would have to be about the origins of a wiki in which Lih talks about the invention of Apple’s Hypercard technology that allowed hyperlinking between electronic documents back in the late 80s.

As someone who’s heard about, but wasn’t around to experience Nupedia, Hypercard, and Usenet, Lih gives a general overview of the technologies, how they came to be, and the role they played in structuring “The World’s Greatest Encyclopedia.”

This book is a joy to read and provides a lot of background information into the inner workings of Wikipedia. Plus, you can pick up a copy of the book for only $10 on Amazon — quite a steal in my opinion.