This came to me as a learning from my first Cordova(phonegap) application development.
The first thing one comes across while developing in Phonegap is "the need for a GUI lib" and the first thing to get in a search result is jQuery, its mobile version and the UI lib. There are many other good libs out there, but this one seems quite ok. While one may choose to use a UI lib or build own lib its up to the developer. In my experience its easy to get started with jQueryMobile and its UI, which uses "Theme roller" to theme the UI.
If one is using jQueryMobile then the trick is to try and solve all the UI problems with this lib itself (not hacking the CSS and JS all over the place in the project). That way the performance will be more and pain to solve all the UI problems is less.
One can just start to make one Cordova application without any libraries, but to be productive soon, the minimum required libraries are
Now the most important library which might not be required for the project as a project dependency but is a real time saver is
After some playing around with the library and from the suggestion from the community I found Lo-Dash library, which is a drop-in replacement for UnderscoreJS with performance enhancements. So I would recommend using
Target platform and the library support :
The current Cordova lib might not support your required target platform !! Yeah, that is another thing which might take up sometime to know in the beginning. With each release these libraries kind of deprecate support for old platforms, so check that out in the beginning itself.
The same goes for jQuery and jQueryMbile. Check out whether the latest version of the library supports your target platform.
Native Notifications in Cordova is not supported :
jQuery tips :
Adding an element to a page and displaying it :
jQuery "append()" and "prepend()" does not update the UI (or DOM), so the added elements are not visible by default. we can hack it by dispatching a jQuery event called "create", the code will look as below
$("#p_4_content").prepend("hello World").trigger( "create" );
That will tell jQuery to render the UI again, resulting in displaying the added item.
Defining EventHandler Scope :
Another nice thing is calling the event handler in required "scope". The jQuery library provides a handy method for adding event event handlers as
$('#id_btn').on( 'tap', onBtnTapped );
But then it will be scoped to the same scope as where its being written. If you are writing things in an Object, you might want to get the "scope" in the handler(which is "this"), in order to do that, jQuery provides a "third" parameter option, and one can pass the scope in there. The optional parameter is at the middle instead of at the end (as comparing to other object oriented programming convention)!! But then its the way to go. So the modified code will look as below
$('#id_btn').on( 'tap', this, onBtnTapped ); //Look at the middle parameter
//and the handler code looks as below
//just saving the scope, may be we need it in future here
var that = event.data; //here event.data=this (which we passed as second param)
That way inside the handler we can get the "scope" as below
var that = event.data;
The second parameter sent while binding the handler to the event, can be got inside the event handler as "event.data". Since we are just passing "this", we can get that in the handler as the example shown above.
Writing the EventHandler :
Well, now the trick writing an eventhandler without making the application behave unreasonably is a challenge. It might sound silly but it is not. If you write an event handler as
Then its bound to get in your way of the behavior of your application. The jQuery fix is to do a "return false" in all the handlers. But then that might not be the case of your handler as that might return in between the code itself. So the fix is make a call to "preventDefault" as soon as you are inside the handler method. the modified code will look as below
That is the start, I will post more tips as I fight through the scenarios.