fancyBox - Fancy jQuery Lightbox Alternative Infographics Dos and Don’ts | Strategy Internet Marketing Infographics are a way to deliver data visualisation to an audience. They’re not just about data visualisation though; the data is presented within a story to communicate a specific message. They can spread like wildfire online and there are a few reasons for this. First of all, visual data is more memorable and has more impact than straight-up facts. The second reason for the widespread use of infographics on the web is the fact that they can add a lot of value to a web site and make visitors want to actually check out its content, while encouraging interaction. Good content and good user experience are what make or break a website these days, and infographics are meant to help with that. Pretty Data Isn’t Data Visualisation Like I mentioned earlier, an infographic is data visualisation told through a story. Here is an example of how not to do an infographic. What’s wrong with this infographic? For starters, the circles sizes could mirror the statistics. Misleading Visualisation Conclusion
3 reasons why you should let Google host jQuery for you All too often, I find code similar to this when inspecting the source for public websites that use jQuery: If you’re doing this on a public facing website, you are doing it wrong. Instead, I urge you to use the Google Hosted Libraries content delivery network to serve jQuery to your users directly from Google’s network of datacenters. Doing so has several advantages over hosting jQuery on your server(s): decreased latency, increased parallelism, and better caching. In this post, I will expand upon those three benefits of Google’s CDN and show you a couple examples of how you can make use of the service. Just here for the links? If you’ve already read this post and are just here for the links, you’re in the right place! If you care about older browsers, primarily versions of IE prior to IE9, this is the most widely compatible jQuery version: jQuery 1.x (OldIE support) If you don’t care about oldIE, this one is smaller and faster: jQuery 2.x (smaller, faster, and no OldIE support) Better caching
HTML5 Introduction jQuery ASP.NET GridView + jQuery tips and tricks - Part 1 Posted by Sheo Narayan under ASP.NET category on 7/29/2010 for Intermediate level | Views : 175386 If you found plagiarised (copied) or inappropriate content, please let us know the original source along with your correct email id (to communicate) for further action. Rating: 4.8 out of 5 5 vote(s) This article demonstrate how to do CRUD operation using GridView and jQuery seamlessly (without page refresh) and also describes some simple UI effects in ASP.NET GridView control using jQuery. This is the Part 1 of this article. Introduction GridView is an unavoidable control while developing any application. In this article, I will demonstrate how to do CRUD (Create, Read, Update, Delete) opeations using GridView and jQuery seamlessly and will also give some simple GridView and jQuery UI tips, like selecting records, highlighting records and deleting records by double clicking it. This is Part1, please read part 2 of this article here. Video of this Article Pre-requisite Code listing - 1 using System;
jQuery UI Getting Started with Sass CSS’ simplicity has always been one of its defining, most welcome features. CSS style sheets are just long lists of rules, each consisting of a selector and some styles to apply. But as our websites and applications get bigger and become more complex, and target a wider range of devices and screen sizes, this simplicity—so welcome as we first started to move away from font tags and table-based layouts—has become a liability. While some have offered proposals on how to fix CSS—adding constants or variables, for example—none have been implemented by any browser manufacturers. And even if a browser did implement a newer, better, extended CSS, it could be years before the new syntax is supported well enough in all browsers for it to make sense to use it. Fortunately, a few years ago developers Hampton Catlin and Nathan Weizenbaum proposed a better way to maintain a complicated stylesheet. So in Sass 3.0 the developers introduced a new, more CSS-like syntax called SCSS (or “Sassy CSS”).
Tutorial start - ASP.NET Ajax Tutorial