background preloader

Google Cloud Storage - Introduction

Google Cloud Storage - Introduction

Basic Shapes – SVG 1.1 (Second Edition) Contents 9.1 Introduction SVG contains the following set of basic shape elements: rectangles (including optional rounded corners), created with the ‘rect’ element,circles, created with the ‘circle’ element,ellipses, created with the ‘ellipse’ element,straight lines, created with the ‘line’ element,polylines, created with the ‘polyline’ element, andpolygons, created with the ‘polygon’ element. Mathematically, these shape elements are equivalent to a ‘path’ element that would construct the same shape. 9.2 The ‘rect’ element The ‘rect’ element defines a rectangle which is axis-aligned with the current user coordinate system. ‘rect’ Categories: Basic shape element, graphics element, shape element Content model: Any number of the following elements, in any order: Attributes: DOM Interfaces: SVGRectElement Attribute definitions: x = "<coordinate>" The x-axis coordinate of the side of the rectangle which has the smaller x-axis coordinate value in the current user coordinate system. y = "<coordinate>" <? <? <?

d3.js Products | Amazon Web Services Amazon Web Services offers a broad set of global compute, storage, database, analytics, application, and deployment services that help organizations move faster, lower IT costs, and scale applications. These services are trusted by the largest enterprises and the hottest start-ups to power a wide variety of workloads including: web and mobile applications, data processing and warehousing, storage, archive, and many others. Amazon Web Services provides a variety of cloud-based computing services including a wide selection of compute instances which can scale up and down automatically to meet the needs of your application, a managed load balancing service as well as fully managed desktops in the cloud. Sign up with Amazon Web Services and receive 12 months of access to the AWS Free Usage Tier and enjoy AWS Basic Support features including, 24x7x365 customer service, support forums, and more. Amazon EC2 provides resizable compute capacity in the cloud. Learn more » See pricing details »

Bare domain name (no-www) | FAQ - NearlyFreeSpeech.NET By default, this is the correct behavior. Using URLs of the form creates a number of problems, and we strongly recommend that you avoid it. Some of the limitations are: It creates noncanonical URLs for your site. Although we don't recommend the practice, you are still welcome to use bare domains with our service. We strongly encourage you to consider the alternatives and implications before using the bare domain name. You can add the example.com alias to your site and enable hard canonical type setting.If you have NearlyFreeSpeech.NET DNS and are using your domain with a site hosted here, you can enable this option by selecting the "Add Bare Domain Forward" action on the DNS information page for your domain in our member UI. If you have NearlyFreeSpeech.NET DNS, the behavior of is summarized in the "Domain as alias" line on your domain's DNS information page.

weepy/o_O - GitHub Microjs: Fantastic Micro-Frameworks and Micro-Libraries for Fun and Profit! Build Management for Javascript, Coffescript and Friends - Paracode Update, 16-feb: I’ve added Brewer.js to the review. tl;dr Find a tool that can compile coffeescript, take javascripts and vendor javascript libs, join them preserving order, and minify them into one file good for release. Its also been quite a journey and I’ve not to make it tiresome and include all of the details. Custom made concoctions This is the quickest way you can have at setting up a build for your code, and sometimes it is just enough. To do this, you can use plain cat and minify command line libraries with a Makefile, use closure compiler with ruby, or use uglifyjs with node Cakefiles. Dedicated tooling First some words about CommonJS and its module system. This specification addresses how modules should be written in order to be interoperable among a class of module systems that can be both client and server side, secure or insecure, implemented today or supported by future systems with syntax extensions. stitch With it, you can use CommonJS in your browser. hem sprockets Brewer.js

How A Missing Favicon Broke My App for Chrome Users Excuse me while I let off some steam. I’ve just spent many hours debugging an authentication issue that was preventing Google Chrome users from logging into a PHP web app we’re currently working on. Here are the gory details for your amusement. The app uses OAuth to authenticate against the client’s central auth service. That means instead of logging in to our app directly, the process is more like signing into Twitter from a third party – we send the user away to log in, they authenticate on the central server as normal and get sent back to us with a token which we can then use to log them in to our app. The issue we were seeing is that Chrome users were clicking the login link, being sent out to authenticate, coming back and still being told they weren’t logged in. As I went through debugging, it became clear that the point at which the process was failing was when the CSRF tokens were being compared. Usually, if sessions go awry, the best thing to do is turn to the raw HTTP headers.

JavaScript: Warts and workarounds When warts collide: var versus with Lexical block scope in JavaScript is broken, and though the use of with is generally considered poor form, it's a good solution to this problem. In most curly-braced languages, blocks delineate lexical scope. { int i = 13 ; { int i = 42 ; print(i) ; } print(i) ; } this code prints 42 and then 13. But, in JavaScript: { var i = 13 ; { var i = 42 ; console.log(i) ; } console.log(i) ; } this code prints 42 and 42. In JavaScript, only functions introduce a new lexical scope and variable declarations are implicitly hoisted to this level. For instance: function f () { var i = 13 ; { var i = 42 ; print(i); } print(i) ; } Is equivalent to: function f () { var i ; i = 13 ; { i = 42 ; print(i) ; } print(i) ; } Aside: Hoisting under the hood JavaScript takes hoisting to extremes. The following program -- a lone reference to x -- provokes a reference error: x ; // ReferenceError: x is undefined but the following program is OK because var x gets hoisted: x ; // No problem! More

Two Game Changing CSS 3 Features - CodeBrief HTML and CSS has always been filled with frustration when it comes to being able to intuitively create layouts and designs. Web developers have long since sacrificed ease of implementation for accessibility and semantic purity. Basic layouts and simple aesthetics frequently require very non-trivial implementations. This is especially apparent to developers who have tasted the forbidden fruit of other platforms such as Flex, Android, et al. Until the near future. Flexible Box Layouts The CSS 3 spec has introduced a new module which is supported by all major non-IE browsers as well as the IE 10 preview. Gone are the days of forcing a layout into a float-based implementation. Anyone coming from a Flex or Android background will immediately see the value of this. For example, consider the following layout: Child One Child Two Child Three Child Four With the associated markup (styling and browser-specific markup removed): Nine Grid Backgrounds Consider the following image: With the associated markup:

HTML5SQL.JS robertpiira/ingrid - GitHub Deft | Open Source Web Server Using jQuery, Plugins and UI Controls With Backbone Most Backbone applications either use jQuery or Zepto as their DOM manipulation of choice. I tend to use jQuery as it’s supported across more browsers and has more features – though it is a little heavier in terms of download size (and maybe performance). I also use a lot of jQuery plugins for various controls, to create specific effects, etc. It’s generally easy to do, as Backbone’s views provide direct access to a jQuery element as “this.el” or “this.$el”. From there, we can call standard jQuery code and plugins. There are some common patterns I’ve noticed for doing this, too. DOM Dependent/Independent At a very basic level, jQuery manipulations of the DOM can fall in to 1 of 2 categories: DOM-dependent and DOM-independent. For example, it doesn’t make much sense to call “.slideUp” if the HTML we’re manipulating isn’t currently displayed. On the other hand, I often call “.hide” on document fragments before they are attached to the DOM. Simple Manipulations And Events

Related: