I would like to share some observations and my knowledge in this article with umumble readers.
Let’s do it!
1. Write as you say it aloud
Your task is to show other programmers that you do it with a little twist.
Before you write the next piece of code, think and say it out loud what you are going to do. For example, I need to clear little bit this item. Many people will write without any hesitation:
$(".info").html("")
Well, congrats! Here is another new one ... Why is it better than others?

1. It is brand new! If someone is going to do something, he usually thinks: whether there is any sense to do that, and if there is some, he does it.
2. It is really fine one! You just get and use it. In addition, it is based on Bootstrap and Glyphicons.
3. File Upload widget with multiple file selection, drag & drop support, progress bars and preview images for jQuery.
4. It supports cross-domain, chunked and resumable file uploads and client-side image resizing.
5. It works with any server-side platform (PHP, Python, Ruby on Rails, Java, Node.js, Go etc.).
blueimp.github.com / jQuery-File-Upload /
Browser support:
github.com/blueimp/jQuery-File-Upload/wiki/Browser-support
Every new technology has its own comparisons with its competitors as jQuery is closely compared with Flash. Flash was the technology used by many web designers a while ago, but now it’s the turn of jQuery to add the special effects or interactivity to a website. jQuery makes it easier to create sophisticated custom effects and animations compared to Flash. This article provides some fantastic examples with amazing results, which can be achieved using standard browser and your imagination.
Apple like retina effect

Introduction

I needed dropdown tree in order to implement the current project. Since I have already used jQuery plugin TreeView and its functional suits me, so I decided to make dropdown tree on its basis. As a result, I got plugin DropDownTreeView that I want to share.
Functional
This plugin allows creating dropdown trees that are loaded with AJAX. When a tree is created, an opening tree button is added to an object wrap, and a tree is loaded. The tree can be loaded as a whole and partially (it is useful for large trees). HTTP requests can be performed by POST and GET methods. HTTP request parameters are determined by the user. The tree is built by jQuery.Treeview. The tree is minimized by selecting the item and clicking out of the tree range.
Here are using examples with a description
1. Adding styles for jQuery.Treeview and jQuery.Treeview.DropDown
<link href='jquery.treeview.css' type='text/css' rel='stylesheet'>
<link href='jquery.treeview.dropdown.css' type='text/css' rel='stylesheet'/>

After a year of development the final gold version of jQuery Mobile 1.0 based on jQuery 1.6.4 has been released (support for jQuery 1.7 will come with a version of jQuery Mobile 1.1). The framework is designed to develop sites with the touch interface using usual HTML, CSS and JavaScript. Tools like PhoneGap allow easily transforming the site HTML5 into a mobile application and distributing it through the app stores.
jQuery 1.7 is ready to download! You can download jQuery CDN:
code.jquery.com/jquery-1.7.js
code.jquery.com/jquery-1.7.min.js
Also, this release will be available to download from Google and Microsoft CDNs within a day or two.
JQuery team thanks all who have participated in the testing and finding bugs in the beta-versions, as well who believes in the strength and stability of the release. In addition, they are asking anyone who finds any bugs to report about them on the bug-tracker, and if it is possible to do the replay tests on jsFiddle for the faster problem analysis.
What is new in the version 1.7
You can quickly review a short list of new features on jQuery API with a tag 1.7, and below is given a description of version 1.7 innovations, as well as some things that are not included in the documentation for API.
Often, there are tasks that require to map a tree structure of interaction of any entity. For example: navigation through the file system, menu of the site or the content of the textbook.

jQuery 1.7 beta 1 was released.
.on () and .off ()
bind, live and delegate could work unpredictably when use together. For example, $(document).unbind ('click') removes all live ('click')-events from the entire document.
New API events .on () and .off () is designed to unify the system of generation of event handlers:

It is a fairly typical task, when the pattern of its solution usually is called as a waterfall. The implementation of this pattern is node.js, although some people work in the browser - async.
But we do not want to include the entire module for a single method as well as the copy / paste. The callback function is passed to async, everywhere we used the jQuery.Deferred. There is no difference, but we do not want to “break” a design style :)
As a result, there is written a small utility similar to jQuery.when
Unlike to the jQuery.when, the functions and their return should be passed by arguments, and not jqxhr, otherwise sense of waterfall will be lost. Although, it will not cause the error, because the waterfall accepts any argument’s types.

An article is dedicated to the plug-in, which simplifies the existence of client-side for a programmer.
When filling out the form happens that the form needs to be changed, considering the inputted data (hide and show the fields). The simplest example is when we order the delivery of goods, the user has selected an option “pickup”, and then the fields about the delivery address can be hidden, but it would be nice to show the map with directions for “pickup”.
What is next?
Often, such logic remains without realization, but if we care about the users, then it should be done.
The first standard approach is to make a step wizard, where the form is generated for each step on the server’s side. Some people think that this is a bad option, because it requires the dreary work of splitting the process into steps, writing tons of code, and there is no the pleasure working with this form.
The second approach is to write “puttee” JavaScript that implements all the logic on the client’s side. Especially, it is sad to write “cascading” logic, such as “if (a) was entered into a field A, then show B, if (c)was entered into a field B, then show D. If something else was entered into A, then hides B, and then D”.
Both options are not comfortable. First of all, the logic is realized by the imperative style instead of declarative. But there is way out!