- RT @gblock: Auth0 Extend offsite. Our team is busy cracking away on an MVP @SalesForceDev and @auth0_extend Integration. /cc:@WadeWegner ht… 13 hours ago
- Not sure how a first day could go any better. Met the founders; met my team face to face. @auth0 was the right move. This is going to be fun 1 day ago
- RT @tjanczuk: Just a coffee break during @auth0 offsite #cancun https://t.co/WCK49vHQCw 1 day ago
- The steady flow of awesome ideas for our platform keep coming. twitter.com/auth0_extend/s… 1 day ago
- Just checked into my room in Cancun. Get to meet my whole team at @auth0_extend tomorrow. https://t.co/Sr679VPXNL 2 days ago
Using the jQuery Template Plugin for Consistent User Notifications
May 31, 2011Posted by on
I recently started playing around with the new jQuery template plugin after seeing Stephen Walther present at my local .NET Users Group. I wanted to share this simple user notification template that I have been using.
It is amazing how little code is needed create a very nice and consistent ajax error notification.
Update: I wanted to pop back into this post seeing as how it is getting some circulation on the internets and go into a little detail on what all is going on here. To start this code sample is a Razor based layout in an ASP.NET MVC 3 application. So, it is the equivalent of a Master Page in ASP.NET. The elements that being with ‘@’ are Razor syntax for rendering server side information into the final markup sent to the browser.
The page consists of a couple divs one of which is classed “ajax-busy” that contains a typical ajax spinner image. While not in the sample code, the ajax-buzy class is not visible by default using CSS rules. The main script block uses the jQuery ajax methods to display the spinner when there is an active ajax call being made.
Near the bottom of the page is a script block of type text/html, this is my client side template for my error notification. This block is ignored by browsers while rendering. To display a message, I add a handler to jQuery’s ajaxError method. This handler first locates the template element by id, then applies the template to a json object that I have created inline and finally appends the result to the body of the html document.
The element is now visible, but I take it a step farther by displaying it as a model dialog using jQuery UI’s dialog widget. With some simple set up of the dialog I handle removing the element from the page when the OK button is clicked.
This bit of functionality is now handled globally in the application by this one chunk of code. Here is what the end product looks like.