Arnold Matusz's Blog

This post may be most relevant to those who haven’t had the chance to work with jQuery yet. Lately there is a great hype around jQuery, very many people talk about it, very many write excellent example but most of them target more advanced users.

jQuery is a lightweight (~19KB Minified and Gzipped) JavaScript library which easily enables us to traverse the DOM (Document Object Model), handle events, animate elements, and do asynchronous requests (AJAX – Asynchronous JavaScript and XML). » Continue reading ...

I’ve been using Firefox for quite allot of time now, and I got used to many extensions I could not live without in the day to day development life. Firebug is one of these. When somebody told me: You can’t call yourself a web developer unless you have Firebug installed, I thought this was a bit to hard. But after I faced many situations where Firebug was the definitive tool, I really think everybody should use it.

I often have to do some work on websites in other browsers (Ex: IE – eeeek I know). This is when I really feel I like and I miss Firebug. I really love to see how asynchronous requests are performing (network monitor), I really love how you can inspect and edit DOM elements, I really love to edit the DOM on the fly and see the effects instantaneously, I really love to edit the CSS on the fly and see the effects, you guessed it: instantaneously. I also love that it has got a JavaScript Console where I can test my jQuery magic on the fly. Then there is the fact that it logs JavaScript errors and I also need to mention I love that I can debug JavaScript with it. » Continue reading ...

In my last post I blogged about how jQuery $(document).ready() and ASP.NET Ajax asynchronous postbacks can be made to behave well together. The issue is that normally $(document).ready() is called when the DOM is ready to be manipulated. But this doens’t happen after an ASP.NET Ajax asynch postback occurs.

This means that the initial jQuery bindings won’t be automatically available after the asynchronous postback is over. I underline “automatically” here because my last post describes more possibilities, how this issue can be worked around. » Continue reading ...

I’ve been a bit skeptic about the thought of combining ASP.NET Ajax with jQuery, partly because I didn’t really know what the impact was going to be. But jQuery is very fast, very appreciated throughout general opinion, there are extremely many plugins available for free, writing your own plugins only requires little JavaScript knowledge (opposed to writing your own extender in .NET, like controls in the AjaxControlToolkit).

To be sincere, there is a very short learning curve so there is no reason for not trying jQuery. I’ve tried with regular web applications, but when I coupled jQuery with ASP.NET Ajax on little niggle stood out. » Continue reading ...