John Beales

I just finished reading a story that’s quite different from anything that I’ve read before. The story is Evangeline, A Tale of Acadie by Henry Wadsworth Longfellow. It’s a poem telling the story of Evangeline, a young Acadian girl. Her wedding day is the day of Le Grand Dérangement, and she is separated from her husband-to-be and spend the rest of her life searching for him.

I had never heard about Evangeline until I went to the maritimes with my sister two summers ago. When we were there we found all sorts of things called Evangeline. On the tourist maps there the Evangeline Trail, (a driving route in Nova Scotia), and part of New Brunswick, at lest on the tourist maps, was referred to Evangeline’s Land. There are all kinds of places called Evangeline, the Evangeline Inn, even the Evangeline Credit Union.

At some point before my 2007 trip to the maritimes, my fiancée Joanie had told me the story of Evangeline and Gabriel, lovers separated on their wedding day, who spend the rest of their lives searching for each other. There is even a song that plays on the radio here in Québec, and has for years, with the story. However, at the time neither of us realized that Evangeline was an Acadian.

So, interested to know who Evangeline was, my sister and I kept our eyes open and I ended up getting a copy of Henry Wadsworth Longfellow’s poem, Evangeline, a Tale of Acadie for my fiancée as a gift. This is the poem that started the modern fascination with Evangeline, and is largely responsible for our awareness today of what happened on September 5, 1755, when an entire culture was forced from what had become their homeland and scattered around the globe.

Evangeline tells the story of a part of Canadian history that is not well taught in schools, at least not in the west where I grew up. I remember learning about the Acadians, and learning that they were sent away at one point, but I don’t remember it being presented as any type of tragedy, I remember it being taught as something that had to be done, after all, they spoke French, and Canada was British territory. Now, years later, I finally learned that deporting the Acadians was not simply business as usual. In fact, it ranks up there among the worst things done to a group of people in Canada. This past summer Joanie and I went to the maritimes and we had the chance not only to go to Grand Pré and learn more about life as an Acadian and the deportation, but we were lucky enough to be in Caraquet, New Brunswick, (the “Capital of Acadie”), during the Acadian World Congress, so we got to experience modern Acadie, and it’s a culture that we should try to hold on to here in Canada, (and always should have tried to hold on to).

Back to the poem, it’s a long poem, long enough that it’s printed as a book, but it’s not hard to read, (I don’t exactly read poetry all of the time), and I highly recommend it. For Canadians, it is a window into a time and events that form an important part of our history, for Americans it gives you a glimpse of the birth of the Cajun culture, and for all of us it inspires us with a story of faith that most of us rarely even imagine.

Over the last several days I’ve been enjoying short stories written by one of my favourite authors, Jeffrey Archer. His book, Cat O’ Nine Tales, is a collection of short stories based largely on stories he heard in prison. It’s been on my shelf for quite a while, (I think I received it last year for Christmas in 2008), and for some reason I haven’t picked it up, a mistake I will try to avoid in the future.

It’s refreshing to change from the longer books that I’ve been reading to short stories. They’re fun to read and each one doesn’t take too long, especially when they’re as engaging as these ones.

I have another Jeffrey Archer book that I haven’t read, Shall We Tell the President but I’m told that I should read The Prodigal Daughter first, and I don’t have that one, so I am keeping my eye out for a copy.

I’ve turned johnbeales.com and @johnbeales red for the 2010 Olympic Games in Vancouver. Join me and do the same for your blog, Twitter profile, or both.

Look how awesome my twitter profile looks all decked out for the Vancouver games:

You can do the same. Here’s a ZIP file containing the PSD Source, and PNGs of both my Twitter background, (with the text), and the blog background, (without the text).

Go nuts, and let me know here or on Twitter about it!

Edit: Here are direct links to the backgrounds with text, and without text.

After reading about the economy and about Javascript it was time for some Fiction. I received a copy of Up in the Air, (the book that they based the movie on), for Christmas that’s just been sitting on a shelf so I pulled it out and read it.

I haven’t seen the movie, (although I will probably rent it when I can), but had read some reviews that were critical of it because, at least according to the reviews, we’re supposed to feel sorry for Ryan, (the George Clooney character), and he’s a guy that goes around the country firing people, essentially making their jobs miserable. I’m not sure if it’s a difference of interpretation, or if things have been sensationalized for the movie, but in the book he’s the guy that “counsels” employees right after they are fired, mostly to stop them from suing. It’s not much better, I know, but it does seem slightly better. In the book, though, we really get inside Ryan’s head, which can be a confusing place at times, and we see what he really thinks about his job, the people around him, and the world. It’s especially interesting to see how his impressions of people change over the course of the story.

I’m really interested to see if we get the same level of intimate access to Ryan in the movie as we do in the book, and how they made the jump in general. If the movie is half as interesting as the book, it should be an interesting film to see.

I’m working on a project now were we’ve decided to go with as pure HTML5 as posible, and it’s a breath of fresh air. Things work more or less how they should, and Internet Explorer is even playing along, with a little help. Getting started was a bit of a trick, though, as it can be hard to find information on how HTML5 works without diving into specification documents, which is never fun, or easy, (if you don’t want to read the story, skip straight to the resources).

I hadn’t been following the development of HTML5 with more than a passing interest. I figured that when it was ready, then I would start using it. I also understood that there were different parts that may reach completion at different times, and was keeping my eye open for some sort of “completion” signal. 2009′s 24 Ways was that signal for me. There were several articles on using HTML5 features along with their CSS3 counterparts, and enough evidence that browser support is there to start my investigation.

Here’s the deal: Basic HTML5 support is pretty good in webkit-based browsers, alright, (read usable), in Gecko, and kind of lacking in Internet Explorer. However, if you can rely on Javascript being present, (which I can in my project), there’s an HTML5 Shiv Javascript by Remy Sharp that makes it so that you can style HTML5 in Internet Explorer. Add it using a conditional comment and you’re good to go.

So, we have useable cross-browser support, but where do we turn to learn about which tags are in, which are out, the correct doctype and mime-type, and all that? We could read the specification, (and we will have to read a bit, at least), but it would be nice if there was an introduction to HTML5 somewhere. It turns out that Robert Nyman has written an Introduction to HTML5. It’s detailed enough to get you started, but not so detailed that you get lost, (like the spec), and if you’re looking to be convinced of the value of HTML5, check out HTML5: Tool of Satan, or Yule of Santa?, Have a Field Day with HTML5 Forms, and Breaking out the Edges of the Browser from 24 Ways 2009.

Once you dive a little deeper you’ll find that there are elements of HTML5 that you need more in-depth information for, so it’s time to turn to the spec. However, there are 2 groups, (W3C and WHATWG), working on HTML5, and therefore 2 spec documents, (fun!). Fortunately, the two groups have the same editor, so they’re more or less working on the same thing. I find the WHATWG HTML5 document easier to read, but if you prefer the W3C version, go nuts.

Finally, the whole content-type debate that’s been going on for what seems like centuries is still a mess. In HTML5 you’re supposed to include a Document Type Definition and there should be no namespaces on the HTML element if you’re serving as text/html, and you’re supposed to serve in application/xhtml+xml if you want to use namespaces, or force XML validation, or anything like that. The problem is that Internet Explorer really doesn’t like application/xhtml+xml, (it shows the raw XML document), so if you need a namespace for some reason, (for example, you want to use Facebook Connect on the site), you can’t serve valid markup.

So, that’s it. HTML5 has arrived, or at least parts of it. If you can rely on Javascript being present, or rely on IE users not using your web app, you can go ahead and start using it. Here’s a quick recap of the resources:

• Introduction to HTML5 by Robert Nyman
• HTML5 Shiv Script by Remy Sharp
• HTML5 Spec from WHATWG and the W3C
• From 24 Ways 2009:
  • HTML5: Tool of Satan, or Yule of Santa?
  • Have a Field Day with HTML5 Forms
  • Breaking Out the Edges of the Browser, (also by Remy Sharp)