It has been a while since we have committed anything in the project, but we have been improving it and using it many of our internal and client applications. It is time now to push some more updates. We have updated the framework with jQuery Mobile 1.4, Backbone 1.1.1 and Underscore 1.6.0.

Please do checkout and provide feedback.

Ember.js is a modern and rapidly growing javascript framework. As they promote on their landing page, it is truly “A framework for creating ambitious web applications”. Ember takes away lot of boilerplate code, and support excellent binding for object properties and Views.

Many people are awaiting for 1.0 eagerly, including myself.
Only weak point I see right now is Documentation and getting started for mid to large sized application.

Ember has a nice writeup about Ember Application architecture.
But there is no complete and minimal example code available.

Here is a simple fiddle of Ember Routing + Ember-Data.

For full-screen result (so URL hash changes are visible)

Popular Todos demo application built with the backbone-jqmobile framework.

Demo shows how easy it is to develop mobile application with backbone-jqmobile framework.

Full Page Demo here

Full source available here

More demos are available at -

Another demo application built with the backbone-jqmobile framework. This time I have taken example of Employee Directory, a popular backbone based application built by Christophe Coenraets. There are set of feature I have not implemented in this demo app and have keep it simple to demonstrate the usage of the framework.

Full Page Demo here

Full source available here

More demos are available at -

A small application is built to show the usage of our framework backbone-jqmobile

The example shows the detail use of the framework and how a working application can be developed quickly.

Full page demo here

Full source available here

More demos are available at -

To make HTTP request to remote services, we have to use Meteor.http package.
Meteor.http package can be added to project by command “meteor add http”.

Meteor.http supports both synchronous and asynchronous requests. But in this example/usecase, we want to return results to client. And Meteor by default supports synchronous services on server (which conflicts with node.js asynchronous model), so I will use synchronous Meteor.http api in this example.

var url = 'http://.....';
var result = Meteor.http.get(url, {timeout:30000});
if(result.statusCode==200) {
    var respJson = JSON.parse(result.content);
    console.log("response received.");
    //custom code
    if(respJson.message.code == 0) { //IF OK
        console.log('returning response');
        return respJson;
    } else {
        throw new Meteor.Error(respJson.message.code, respJson.message.text);
} else {
    console.log("Content issue: ", result.statusCode);
    throw new Meteor.Error("");

Full source code is available at
Live demo (twitter):

Default Phonegap way of interacting with the Native code is to initiate a plugin request from Javascript, process in the Native code and reply the result with data which can be used in Javascript again. However many times it may require to update Javascript values or HTML DOM elements without initiating any plugin call from Javascript. Below code snippet uses a Plugin method as a gateway to call a Javascript method from Native Android code.

Example with full source code for Android is available here

By default PhoneGap File API creates only one directory at a time and the developer has to write the additional code in case nested directory structure is required. Below is an example of a small utility method which creates the nested directory structure based on the given path.