Ian Michell

We've been going through the process for getting cochlear implants for my son Thomas... Last we heard was that we had a yes from Great Ormond Street Hospital and were expecting a wait of at least 30 days for that to come through and surgery probably about a month afterwards...

My wife Sadie got the call yesterday telling asking if they can operate on Thomas next Wednesday!

Some say that the NHS is slow, but blimey, after months of assessments the date for surgery came quickly...

First day back at ProcServe. Few new people to meet, lots of friends to enjoy.

I recently discovered handlebars, a javascript template framework. If you take a look at the tutorials on the website itself you will notice that all of the tutorials focus on declaring your templates in <script> tags.

The project itself does not support remote templates, unless you have them precompiled...

This very brief guide is to illustrate to you how you would automatically load and compile remote templates using jQuery.

First create a template called post.handlebars (or whatever else you decide) and insert the following code:

<div class="entry"> <h1>{{title}}</h1> <div class="body"> {{body}} </div> </div>

Next add the following line into your main html file (e.g. index.html):

<link rel="prefetch" type="application/x-handlebars-template" src="handlebars/post.handlebars" data-template="post" />

Next add the following javascript to your markup (or separate javascript file). Remember it's usually better to add the markup at the bottom of your body.

var handleBarsTemplates = {};

$(function($) {

$("link[type='application/x-handlebars-template']").each(function() {

var url = $(this).attr("href");

var templateName = $(this).data('template');

$.get(url, function(data) {

var template = Handlebars.compile(data);

handleBarsTemplates[templateName] = template;

});

});

});

You can access the templates by using the following javascript:

handleBarsTemplates.post({title: "Easy Handlebars", body: "This was really simple wans't it"});

For the first time in about 6 years, I'm finding myself writing pure C code in anger... Long gone are the terrible days of Makefiles, segmentation faults and bad memory leaks...

The project I am writing in C is actually an access restriction module for apache! Although fun, I have found myself actually spending more time reading code from the mod_rewrite module in apache, due to the absolute horrendous documentation.

I would like to mention that I have found Netbeans C/C++ support outstanding and it's code completion and API Documentation parsing (for those that don't know what that is: /** or /// as comments above a method declaration).

One of the things I love about rails 3.x is it's support for unobtrusive javascript (UJS). If you've been living under a rock for the past few years; UJS is about wiring javascript into your markup using HTML 5 data attributes (most common method anyway).

One of the things I hate about AJAX frameworks is the lack of proper support for accessible devices and most traditional ways of enriching your markup with javascript are binding events to elements directly using the on* attributes (I could keep this up all day).

Down to business.

The simplest way I found to enrich my grails application with javascript was to make use of RoR's jquery-ujs.js script found: https://github.com/rails/jquery-ujs.

Simply add it to the js folder in your web-app (<project>/grails-app/conf/ApplicationResources.groovy) folder in your grails application and then add it to your application resources file:

modules = {

    ...

    ujs {

        resource url: 'js/jquery-ujs.js'

    }

}

Then include it in your GSP files with:

<g:javascript library="ujs" />

Once you've done that you simply add:

data-remote="true"

To your forms, buttons or links (check the rails documentation on this subject for more information, or simply read the script itself.

You're probably thinking, "great... But nothing happens to my page. I can see the data posting to the server, but nothing comes back."

Well in order to make something actually happen, you need to hook in a bit of javascript:

(function($, undefined) {

    $('*[data-remote]').live('ajax:success', function(e, data, status, xhr) {

        ...

    }

});

And you can process the response by using what's returned in the data variable.

(function($, undefined) {

    $('*[data-remote]').live('ajax:success', function(e, data, status, xhr) {

        var update = '#' + $(this).data('update');

        if (update !== undefined) {

            $(document).find(update).replaceWith(data);

        }

    }

});

As you can see above, I have simply made use of another data attribute data-update="updateElementId" to identify the element I wish to update. I then put the following code in my controller to send back a fragment of html:

if (request.xhr) {

    render template: 'myFragment', model: [myModel: someFormModel]

}  else {

    [myModel: someFormModel]

}

The code above means that you will have to use GSP fragments to send back HTML to your javascript code asynchronously. However by doing this, it means that if your users don't have javascript enabled (and they should be shot), you will simply end up with the whole lot (i.e, your browser will process the form / link request as expected).

There is no reason you can't set everything up to json either! Simply add data-type="json"  to your form / link element:

<g:form name="myForm" action="myAction" data-remote="true" data-update="elementToUpdate" data-type="json">

There we go! Wasn't so hard to do was it? You will now have graceful rich applications, that fall back to being fairly basic should your users not support HTML 5 or javascript.

Had our first appointment with the good doctors at Great Ormond Street Hospital. It was interesting taking Thomas through his hearing test (as it was the first time I had done one like this with him).

Had a good deal of information given to us by the consultant and now we get to move on to the next round; starting with a CT scan and a few more tests.

Looks like he will get bilateral implants and if done quickly (which we want) means he may be able to go to a mainstream school! The only downside is he will probably never get to experience rugby!