About two months ago, John Resig and I met at Café Algiers in Harvard square to discuss how Microsoft can contribute to the jQuery project. Today, Scott Guthrie announced in his second-day MIX keynote that Microsoft is throwing its weight behind jQuery and making it the primary way to develop client-side Ajax applications using Microsoft technologies.
What does this announcement mean?
It means that Microsoft is shifting its resources to invest in jQuery. Developers on the
ASP.
NET team are now working full-time to contribute features to the core jQuery library. Furthermore, we are working with other teams at Microsoft to ensure that our technologies work great with jQuery.
We are contributing to the open-source jQuery project in the exact same way that any other company or individual from the community can contribute to jQuery. We are writing proposals, submitting the proposals to the jQuery forums, and revising the proposals in response to community feedback. The jQuery team can decide to reject or accept any feature that we propose.
Any feature that Microsoft contributes to jQuery will be platform neutral. In other words, Microsoft contributions will benefit
PHP and RAILS developers just as much as they benefit
ASP.
NET developers. Microsoft contributions to jQuery will improve the web for everyone.
Contributing Support for Templates to jQuery Core
Our first proposal concerns templating. We want to contribute support for templates to jQuery so that JavaScript developers can use jQuery to easily display a set of database records. You can read our templating proposal here:
http://wiki.github.com/nje/jquery/jquery-templates-proposal
You can download and play with our prototype for templating here:
http://github.com/nje/jquery-tmpl
The following code illustrates how you can use a template to display a set of products in a bulleted list:
<script type="text/javascript">
jQuery(function(){
var products = [
{ name: "Product 1", price: 12.99},
{ name: "Product 2", price: 9.99},
{ name: "Product 3", price: 35.59}
];
$("ul").append("#template", products);
});
</script>
<script id="template" type="text/html">
<li>{%= name %} - {%= price %}</li>
</script>
<ul></ul>
The template is contained in a SCRIPT element that has a TYPE=”text/html” attribute. Browsers ignore the contents of a SCRIPT element when they don’t understand the content type.
Notice that the placeholder {%=...%} is used within the template to indicate where the name and price of a product should appear. The delimiters {%=…%} are used for expressions and the delimiters {%...%} are used for code.
Finally, the products are rendered using the template with the call to $(“ul”).append(“#template”, products). The standard jQuery DOM manipulation methods have been modified to support templates. When the page above is rendered, you get the bulleted list displayed in the following figure.
Our goal is to keep our proposal for templates as simple as possible. After support for templating has been added to jQuery, plug-in authors can take advantage of templating when building complex data-driven plug-ins such as a DataGrid plug-in.
The Ajax Control Toolkit
Over 100,000 developers download the Ajax Control Toolkit every month. That’s a mind-boggling number of downloads. We realize that the Ajax Control Toolkit is extremely popular among
ASP.
NET Web Forms developers and we want to continue to invest in the Ajax Control Toolkit.
If you are adding JavaScript interactivity to an
ASP.
NET Web Forms application, and you don’t want to write JavaScript, then we recommend that you use the server controls in the Ajax Control Toolkit. Using the Ajax Control Toolkit does not require knowledge of JavaScript and the toolkit enables you to build applications with the concepts familiar to
ASP.
NET Web Forms applications developers.
If, however, you are interested in creating client-side interactivity without server controls then we recommend that you use jQuery.
We plan to continue to release new versions of the Ajax Control Toolkit every few months. Our goal is to continue to improve the quality of the Ajax Control Toolkit and to make it easier for the community to contribute code, bug fixes, and documentation.
The
ASP.
NET Ajax Library
We are moving the
ASP.
NET Ajax Library into the Ajax Control Toolkit. If you currently use
ASP.
NET Ajax Library client templates, client data-binding, or the client script loader then you can continue to use these features by downloading the Ajax Control Toolkit.
Be aware that our focus with the Ajax Control Toolkit is server-side Ajax. For client-side Ajax, we are shifting our focus to jQuery. For example, if you have been using
ASP.
NET Ajax Library client templates then we recommend that you shift to using jQuery instead.
Conclusion
Our plan is to focus on jQuery as the primary technology for building client-side Ajax applications moving forward. We want to adapt Microsoft technologies to work great with jQuery and we want to contribute features to jQuery that will make the web better for everyone. We are very excited to be working with the jQuery core team.
