Sunday, September 28th, 2008

jQuery finds its way into Microsoft and Nokia stacks

Category: .NET, Ajax, jQuery

>Just as jQuery kicks off its first jQuery conference adjunct with The Ajax Experience in Boston tomorrow, it gets an energy boost from some big double-barrel news:

Microsoft and jQuery

Microsoft is looking to make jQuery part of their official development platform. Their JavaScript offering today includes the ASP.NET Ajax Framework and they’re looking to expand it with the use of jQuery. This means that jQuery will be distributed with Visual Studio (which will include jQuery intellisense, snippets, examples, and documentation).

Additionally Microsoft will be developing additional controls, or widgets, to run on top of jQuery that will be easily deployable within your .NET applications. jQuery helpers will also be included in the server-side portion of .NET development (in addition to the existing helpers) providing complementary functions to existing ASP.NET AJAX capabilities.

Scott Guthrie talks about the news and details some of the features. His blog shows intellisense at work, and more.

Scott Hanselman then wrote an tutorial that shows jQuery working with ASP.NET libraries such as the ASP.NET AJAX 4.0 Client Template work.

Here is the sample code that shows the weaving of jQuery and Client template APIs. The script src at the top is to an “intellisense” version of jQuery, which includes the addition of special comments to make Intellisense work. The Open Ajax Alliance is trying to standardize on this metadata so we can share it between the various tools (e.g. Aptana has a very nice sdoc that does this, and allows you to put it external to the file so you don’t have to have clients download it).

javascript
< view plain text >
  1. var bikes;  
  2. Sys.Application.add_init(function() {  
  3.     bikes = $create(Sys.UI.DataView, {}, {}, {}, $get("bikes"));  
  4.     $(".colorfilter").click(function(e) {  
  5.         LoadBikes($(this).val());  
  6.     });  
  7.     LoadBikes();  
  8. });  
  9.  
  10. function LoadBikes(q) {  
  11.     qq= q|| "Red";  
  12.     var svc = new Sys.Data.DataService("bikes.svc");  
  13.     svc.query("/Products?$filter=Color eq '" + q + " '&$top=5", OnProductsLoaded);  
  14. }  
  15.  
  16. function OnProductsLoaded(result) {  
  17.     bikes.set_data(result);  
  18.  
  19.     $("ul li:even").css("background-color", "lightyellow");  
  20.     $("ul li").css("width", "450px").css("font-size", "12px");  
  21.  
  22.     $("div.bikerow").mouseover(function(e) {  
  23.         $(this).animate({  
  24.             fontSize: "18px",  
  25.             border: "2px solid black"  
  26.         }, 100);  
  27.     }).mouseout(function(e) {  
  28.         $(this).animate({  
  29.             fontSize: "12px",  
  30.             border: "0px"  
  31.         }, 100);  
  32.     });  
  33.  
  34. }  
  35. Sys.Application.initialize();

Nokia and jQuery

Nokia is looking to use jQuery to develop applications for their WebKit-based Web Run-Time. The run-time is a stripped-down browser rendering engine that allows for easy, but powerful, application development. This means that jQuery will be distributed on all Nokia phones that include the web run-time.

To start Nokia will be moving a number of their applications to work on the run-time (such as Maps) and building them using jQuery. jQuery will become part of their widget development platform, meaning that any developer will be able to use jQuery in the construction of widgets for Nokia phones.

How will these companies work with the project?

Microsoft and Nokia aren’t looking to make any modifications to jQuery (both in the form of code or licensing) – they simply wish to promote its use as-is. They’ve recognized its position as the most popular JavaScript library and wish to see its growth and popularity continue to flourish.

In fact their developers will begin to help contribute back to the jQuery project by proposing patches, submitting test cases, and providing comprehensive testing against their runtimes. As with any contribution that comes in to the jQuery project it’ll be closely analyzed, reviewed, and accepted or rejected, based upon its merits, by the jQuery development team – no free ride will be given.

A significant level of testing will be added to the project in this respect. The jQuery test suite is already integrated into the test suites of Mozilla and Opera and this move will see a significant level of extra testing being done on Internet Explorer and WebKit – above-and-beyond what is already done by the jQuery team.

This is great news for the jQuery project.

Related Content:

  • Review: Nokia E61
    Nokia has made no secret of the fact that it covets RIM's BlackBerry market. While Nokia has always done well in the corporate space with its standard...
  • No diversification plans into enterprise market, say Nokia
    Nokia has no plans to diversify into end-to-end enterprise networking products - at least, not yet, said its chief...
  • Review: Nokia E62
    Released only through Cingular, the E62 brings many of the features offered by the Motorola Q to the GSM audience. However, unlike the Q, the E62 uses...
  • Review: Nokia E61i
    The Nokia E61i is an updated version of the E61, which debuted in 2006. This model offers a full QWERTY keyboard in a slim tablet design. It includes...
  • Microsoft's Nokia acquisition brings fresh legs to mobile race
    In this week's Searchlight: Microsoft gets serious about mobile with Nokia acquisition; Android's tasty new OS; the latest NSA jaw-dropper; and...

Posted by Dion Almaer at 2:01 pm
18 Comments

++++-
4.2 rating from 147 votes

18 Comments »

Comments feed TrackBack URI

I bet MooTools was a close second runner up and they only choose jQuery over MooTools just to save an extra byte off the download size. But they don’t understand the power of MooTools.

Comment by Jordan — September 28, 2008

Even those who hate Microsoft should be excited about this news. This is a two-part precedent: never before has an IDE / dev tools vendor given any one particular script library exclusive favor and support. This literally means that the industry is turning on its head and that a de facto standard, for better or for worse, has been chosen by one of the largest dev tool giants on the planet as being significant enough to build on top of exclusively. The other precedent is that Microsoft has bundled a third party open source codebase as a part of their development foundations and core, and that has never happened before, to my knowledge, in the history of the company. It can only mean good things to come in the gradual evolution of the software giant.

Comment by stimpy77 — September 28, 2008

Congrats, guys!

Comment by Tobie Langel — September 28, 2008

What did Microsoft donate money to the jQuery project? imo MS has absolutely no business using anything open-source (internally or externally) unless they started the project as a part of their own original goals–or have some self-apparent and demonstrated investment in the thing. That company should pay for every tool and feature that contributes to their products/value. From my limited perspective this is taking money away from the development community in saved labor/hours and adding that value into their platform. I don’t see that as consistent with MS’s character and prior actions, or fair to the jQuery project. Nokia not so much s60, etc.

Comment by microwave — September 28, 2008

@stimpy

DW has Spry ;) and cs4 will come with great widget adding support for YUI, jQuery and various of other frameworks.

Comment by V1 — September 29, 2008

Great news for Jhon and his team!

Comment by kadnan — September 29, 2008

I’m sure i’m not alone in thinking “eww, Microsoft?” but if nothing else this gives jQuery kudos in the eyes of decision makers who are suspicious of anything which isn’t endorsed personally by Bill Gates himself

Comment by jamiethompson — September 29, 2008

I think it’s great. I’ve been using jquery with asp.net for a couple years now and it’s an excellent match up. Microsoft’s support should definitely be seen as a positive.

Comment by Fyzbo — September 29, 2008

Surprise surprise, an article that mentions jQuery and Microsoft and you’re bound to find at least 1 post mentioning “what about mootools!” and one post moaning about Microsoft.

Working in a Microsoft shop, and also using jQuery heavily on my most recent project, I think that this is great news.

Comment by shypht — September 29, 2008

jQuery has a lot more users than MooTools. It would be silly to go with Moo when so many people are familiar with jQuery.

As for Prototype, is anyone using it for new sites? Seems like it’s fallen off the map to me. jQuery and Dojo seem to have most of the action when it comes to new projects.

Comment by Nosredna — September 29, 2008

@shypht

You’ll also inevitably find someone coming to Microsoft’s defense and complaining about the complainers, just like you did.

Personally, I just found it neat that Scott Hanselman was using Firefox+Firebug (instead of some competing Microsoft product) to show what he was doing.

Comment by mdmadph — September 29, 2008

@Nosredna, FYI

A new version of Prototype was released today.

Comment by Les — September 29, 2008

Interesting. I’ve always felt MS has all its eggs in Silverlight and Ajax is just an annoyance for them. Still not sure where they stand.

Their ASP.NET Ajax effort is just so horrible compared to using any of the open source Ajax libraries (Ext, Prototype, JQuery, etc). Sort of Ajax for people either too lazy to really learn javascript or to married to compiled languages.

The Ajax world has fast passed MS by. With Google’s entry into the browser market, and the lightning fast javascript engines coming from them and Firefox, Silverlight may be already dead.

Perhaps they’re admitting that.

Comment by RichW — September 29, 2008

@RichW
Interesting observation, unfortunately I believe this is mostly to do “damage-control” and not a real shift of focus/interests…

Comment by ThomasHansen — September 29, 2008

@Nosredna: We’re still using prototype for new projects, coupled with Dan Webb’s excellent lowpro.js, which is also available for jQuery.

@Les: Released where? I don’t see any mention of it on any of the usual spaces.

Comment by MorganRoderick — September 29, 2008

I spoke too soon. The new release of prototype.js is available from the downloads page on the prototype site … it’s not mentionend on the frontpage, or in any of the other places … and going from 1.6.0.2 to 1.6.0.3, it looks like mostly bugfixes (and we like fixes).

http://github.com/sstephenson/prototype/tree/master/CHANGELOG

Comment by MorganRoderick — September 29, 2008

@Nosredna: We are also using Prototype for new projects. It still offers a laundry list of features not handled by jQuery, and I personally prefer its direct extension of DOM elements rather than using the crazy array-obscured collection thing jQuery uses. (Not trying to put down jQuery, and I definitely see the value in its approach, I just don’t like it as much.)

Comment by eyelidlessness — September 30, 2008

Excellent thanks

Comment by Remedies — November 19, 2008

Leave a comment

You must be logged in to post a comment.