dojox.storage Welcome to the Dojo Toolkit API documentation. You are browsing version 1.5 of the Dojo Toolkit. Use the selector to the left to change versions. To find the object you're interested in, use the tree to the left...or use the quick links below. To print the documentation, simply navigate to the object of your choice and hit Print. The main packages of the Dojo Toolkit The granddaddy of the Dojo Toolkit. The user interface framework built on top of Dojo. The namespace of additional Dojo Toolkit projects, including things like Charting, the Grid and DTL. Common modules and packages of the Dojo Toolkit The CSS3 query selector engine of the Dojo Toolkit. The return from any dojo/query call, with lots of goodies. The form elements of Dijit, including TextBox, Button, FilteringSelect and a lot more. Layout widgets to help you design your Dijit-based interface, including BorderContainer and ContentPane. The main object of the Dojo Toolkit's amazing Charting library. Object » dojox.storage Property Summary
Advanced Debugging With JavaScript When used effectively, JavaScript debuggers help find and squash errors in your JavaScript code. To become an advanced JavaScript debugger, you’ll need to know about the debuggers available to you, the typical JavaScript debugging workflow, and code requirements for effective debugging. In this article, we’ll discuss advanced debugging techniques for diagnosing and treating bugs using a sample web application. Article Continues Below On accessibility#section2 This article highlights strengths and differences between debugging tools, and shows how we perform advanced JavaScript debugging tasks. The debuggers#section3 With an increasing selection of good debuggers available, JavaScript programmers can gain a lot from learning how to use them. Currently, there are debugging tools available for all major web browsers. Currently, Firebug and Dragonfly are the most stable options. Familiarize yourself with multiple debugging tools—you never know in which browser the next bug will arise.
cjheath/jquery.comet - GitHub Content Filtering Internet Proxy - SafeSquid django - HTML5 Offline storage web framework jQuery Events: Stop (Mis)Using Return False Probably one of the first topics covered when you get started learning about jQuery events is the concept of canceling the browser’s default behavior. For instance, a beginner click tutorial may include this: This function toggles the hiding and displaying of #mydiv, then cancels the browser’s default behavior of visiting the href of the anchor tag. It is in these very first examples that bad habits are formed as users continue to use return false; whenever they want to cancel the default browser action. I am going to cover two very important topics in this article relating to the canceling of browser events: Use the right method for the job: return false vs. preventDefault, stopPropagation, and stopImmediatePropagationTop, bottom or somewhere in the middle: where in the event callback should you cancel default behavior? Use the Right Method for the Job The main reason return false is so widely misused is because it appears to be doing what we want. What return false is really doing 1. 2.
Creating HTML5 Offline Web Applications with ASP.NET The goal of this blog entry is to describe how you can create HTML5 Offline Web Applications when building ASP.NET web applications. I describe the method that I used to create an offline Web application when building the JavaScript Reference application. You can read about the HTML5 Offline Web Application standard by visiting the following links: Currently, the HTML5 Offline Web Applications feature works with all modern browsers with one important exception. Why Build an HTML5 Offline Web Application? The official reason to build an Offline Web Application is so that you do not need to be connected to the Internet to use it. The JavaScript Reference Application works great on my iPhone even when I am completely disconnected from any network. Admittedly, it is becoming increasingly difficult to find locations where you can’t get Internet access. A second, and possibly better, reason to create Offline Web Applications is speed. Creating the Manifest File When Are Updated Files Downloaded?
Sizing and Positioning Fancybox | GiveGoodWeb You’ve probably seen Fancybox all over the place. In a way, it’s the living-successor of ThickBox and Lightbox. I was recently on a project where I had to both size and place it. Sizing it is easy. Google To create and size the fancybox that will open when it’s clicked, you’d just add the following javascript to your page: Note that pixels are assumed, you should not say something like “390 pixels” like you would in css, it won’t work then. So, above we have defined a fancybox that is 390 pixels wide, and 400 pixels high. (Note this is based on Fancybox 1.3 – I can’t say if it’ll work with other versions.) Fancybox puts everything in a layer with an id of “fancybox-wrap” – so we can easily manipulate it with basic css, like so: You can do the same with padding, maybe even positioning. Hope that helps someone!
Performance:Leak Tools Strategy for finding leaks When trying to make a particular testcase not leak, I recommend focusing first on the largest object graphs (since these entrain many smaller objects), then on smaller reference-counted object graphs, and then on any remaining individual objects or small object graphs that don't entrain other objects. Because (1) large graphs of leaked objects tend to include some objects pointed to by global variables that confuse GC-based leak detectors, which can make leaks look smaller (as in bug 99180) or hide them completely and (2) large graphs of leaked objects tend to hide smaller ones, it's much better to go after the large graphs of leaks first. A good general pattern for finding and fixing leaks is to start with a task that you want not to leak (for example, reading email). For example, start with bringing up the mail window and closing the window without doing anything. What leak tools do we have? Leak tools for large object graphs leak-gauge leak-monitor Leaksoup Purify
Head JS Extreme JavaScript optimization 2010 update: Lo, the Web Performance Advent Calendar hath moved Dec 20 This article is part of the 2009 performance advent calendar experiment. Today's article is a second contribution from Ara Pehlivanian (here's the first). There's a Belorussian translation provided by Patricia. Thanks! Ara Pehlivanian has been working on the Web since 1997. There's an odd phenomenon underway in the JavaScript world today. The thing of it is, it's pretty easy to put your foot to the floor and get up to 60 mph. Variables Let's take a look at one of the staples of programming, the variable.Some languages require you to declare your variables before using them, JavaScript doesn't. function doSomething(val) { count += val; }; Does count have a value assigned to it outside the scope of doSomething? Loops Searching the scope chain for where count is declared in the example above isn't such a big deal if it happens once. for (var i = 0; i < arr.length; i++) { } Did you see it? for (var i = 100; i--; ) { } Caching
ColorBox, A jQuery Lightbox A lightweight customizable lightbox plugin for jQuery Fork me on GitHub View Demos Download Released under the MIT License. Source on Github (changelog). Supports photos, grouping, slideshow, ajax, inline, and iframed content.Lightweight: 10KB of JavaScript (less than 5KBs gzipped).Appearance is controlled through CSS so it can be restyled.Can be extended with callbacks & event-hooks without altering the source files.Completely unobtrusive, options are set in the JS and require no changes to existing HTML.Preloads upcoming images in a photo group.Currently used on more than 1.9 million websites. Instructions & Help The FAQ has instructions on asking for help, solutions to common problems, and how-to examples. Usage Colorbox accepts settings from an object of key/value pairs, and can be assigned to any HTML element. Settings Public Methods Event Hooks Hey,