Posts Tagged: mootools

Dec 06

Great APIs can somewhat make up for bad language design

We all have our preferences of what language(s) we prefer.  There are some languages that are cleaner than others, some are more verbose, and then some are more expressive.  Either way, languages are personal and we get used to various idioms and patterns.  Though, with enough use and experience, we can become proficient in any language and/or API.  Some languages make the learning curve a lot steeper, and even once mastered, still can make it quite difficult to accomplish your objective.

Javascript, I think is one of those languages.  Unfortunately we’re stuck (at least for the time being), using this immaturely designed and in many ways incomplete language.  It tries to resemble some OO features, but is inherently a very procedural language.  Though I’m not a big procedural fan, I’ve used languages like Perl and C for many years with great success.  Perl did a better job of resembling OO capabilities though still fail short in many ways.  C though not having any OO facilities, did in time develop patterns of accomplishing some of the OO idioms in various ways.  Javascript, on the other hand does a poor job of being procedural as well.  Procedural languages are all about data and operations on the data.  With that in mind, they should contain various features and idioms that allow easier operations of such.  Though javascript provides an OK API for binding to the DOM and other browser API binding capabilities, its inability to provide a flexible, extensible programming environment for general purpose programming is effecting the quality of Web 2.0 software development.

Recently I watched a presentation by Joshua Bloch, "How to design a good API and why it matters".  Though the context of the presentation was pretty simple, it actually opened my eyes as to what such simple conventions as naming, focus on usability, and not overwhelming the API with the abundance of patterns, etc…, can do to make the API easier and more enjoyable to use.

Although, I learned a great deal from the presentation and vowed to use some of these conventions in my future work, the importance didn’t really strike me, until this week.  We’re currently redesigning our interface in a more Web 2.0 way, utilizing a lot of Ajax with asynchronous REST calls, event queuing, etc…  This of course requires the writing of a great deal of javascript and trying to employ the available features to implement algorithms and various patterns to support the interface.  In keeping with the tradition of not reinventing the wheel, I started looking for a framework to support the features that we need and then provide an abstraction layer on top to support our custom API needs.  Though I found quite a few libraries out there and many of those exploited javascript to its fullest abilities (or I’d rather call them limitations), none struck me as the mootools framework.  Mootools is a compact modular javascript framework, that allows you to pick and choose the features you would like to use.  Besides the modularity of the features, at its core is a framework that the rest of the mootools APIs are build upon.  The core mootools framework, is an API that allows for working with Javascript in a more OO-friendly way.  It provides for better extensibility capabilities, even for those that are not as familiar with javascript’s horrific OO idioms.

My initial abstraction was the Ajax API.  Besides the fact that I had to build something on top of the mootools ajax framework, the API in its current form did not provide the capabilities needed to process REST based requests.  The onFailure property wasn’t available, though we couldn’t process any non-200 http responses.  In a RESTful world, we are using the non-200 response codes for various server-side exceptions by also appending a custom message header that is used to display an error message.  So the first job was to extend the current Ajax class.  This is very easily accomplished in mootools, using the Class API.  The Class has an ‘implement’ function, which basically allows you to redefine any class properties/functions.  Here is a small example of redefining the Ajax ‘request’ function.

  request: function(){, this.url, this.options.async);
      this.transport.onreadystatechange = this.onStateChange.bind(this);
      if (this.options.method == ‘post’){
        if (this.options.contentType == null || this.options.contentType == ”) {
          this.transport.setRequestHeader(‘Content-type’, ‘application/x-www-form-urlencoded’);
        else {
          this.transport.setRequestHeader(‘Content-type’, this.options.contentType);
          if (this.transport.overrideMimeType) this.transport.setRequestHeader(‘Connection’, ‘close’);
          case ‘element’: this.options.postBody = $(this.options.postBody).toQueryString(); break;
          case ‘object’: this.options.postBody = Object.toQueryString(this.options.postBody);
      if($type(this.options.postBody) == ‘string’) this.transport.send(this.options.postBody);
      else this.transport.send(null);
      return this;

In the above redefinition, I add the ability to specify the contentType attribute, which is then used to set the content type of the request.  The default mootools Ajax implementation, only uses the application/x-www-form-urlencoded content type for every Ajax type request.  This is not sufficient for a RESTful API, as the content type is used as a part of the request definition and can be used to identify and process requests on the server side based on the type of data being submitted.

You can also add properties and functions in the same way to any class that is build with mootools core Class functionality.

The next step was to create an abstraction class that will better define the API needed for accessing our REST services.  I decided to utilize mootools to define such a class, though also giving it the flexibility needed to later extend it as needed.  There are also other benefits to using the mootools Class API.  It allows for a standardized object initialization, object properties definition, and an abundance of other features.  Though the main attraction was the beauty of its API.

Here is a small snippet of the new class definition…

var RestRequest = new Class({

    setOptions: function(options){
        this.options = {
          uriContext: ‘rest’,
          contentType: ‘json’,
          onComplete: Class.empty,
          onFailure: Class.empty,
          clazz: null,
          method: null,
          params: null,
      content: null,
      url: null,
        Object.extend(this.options, options || {});

    initialize: function(options) {
        if (this.options.contentType == ‘json’) {
          this.options.contentType = ‘application/javascript’;
        else if (this.options.contentType == ‘xml’) {
          this.options.contentType = ‘application/xml’;
        this.options.url =
          this.constructUri(this.options.clazz, this.options.method, this.options.params);

    postRequest: function(content) {
      if ($type(content) == ‘string’) {
        this.options.content = content;
      var myAjax = new Ajax(this.options.url, {
        method: ‘post’,
        contentType: this.options.contentType,
        postBody: this.options.content,
        onComplete: this.options.onComplete,
        onFailure: this.options.onFailure,

Two common functions that are used above, setOptions and initialize, are used by the Class framework, to allow for constructing and initialization of the object you define.  You define setOptions function to specify the options/attributes (object state) and override any options that are defined in the super class.  (Note, there is no true concept of inheritance in javascript, rather objects are redefined at runtime with new data/functions.)

Initialize is then used as an object constructor.  It is called by the Class framework to instantiate the object.  Instantiate in fact calls setOptions to initially set the option defaults and override them with any options provided to the constructor.

The custom method, postRequest is then defined that basically abstracts the Ajax request to a particular REST based API.

You can then use the above API for making REST request as follows…

var restRequest = new RestRequest({
    clazz: ‘SomeClass’,
    method: ‘some_method’,
    contentType: ‘xml’,
    params: {
        id: ‘1234’,
        some_param: ‘some_param_data’,
    onComplete: function(responseText) { alert(responseText) },
    onFailure: function(response) { alert(response.status + "\n" + response.statusText + "\n" + response.message) },

I hope the above allows one to see how a great API design can make working with a language that we dislike, a lot more enjoyable.  I really advise you to view Joshua’s presentation.  It can be found here (