Since the demo was very fast it just looked like you are popping up some values with alert command. Therefore I modified the demo and added a 2 seconds delay plus a simple loading.

Hope it’s better now.

Well, during developing for DotNetNuke, I realized that I need some sort of plug-in where it can automatically send part of a large form to a WebService,  process the data and return the result in some sort of understandable and functional way. I also didn’t want to use Ajax Panels since I have a bad experience with them making the page too heavy.

I couldn’t use existing jQuery Ajax plug-ins because of two main reasons. First, I wanted the total control over what’s going on and making it as much integrated as possible with DotNetNuke. Next, I really didn’t want the whole page or the only available form in an ASP.NET page to be posted to the server with that huge ViewState field. Instead, I needed the ability to send part of a page in a very light weight way. Therefor JSON was chosen as the format for in-going and out-coming data over jQuery Ajax method, which is very fast and (hopefully) functional.

And this, is the moment ezAjax, the first gadget beside the main project, is born.

I have spent some time and wrote a documentation and a sample application just in case somebody is interested and wants to use it. You can find all about ezAjax here.

By using ezAjax, I am able to quickly send fields of any part of a page to a Web Service getting help from jQuery Ajax method. Actually there is nothing WOW around it but it simplifies the whole process and recognizes FCKEditor elements in a DotNetNuke Page.

I have also plans to develop this plug-in as we go, based on your comments and my future needs.

ezAjax Page