| /* | |
| * object.watch polyfill | |
| * | |
| * 2012-04-03 | |
| * | |
| * By Eli Grey, http://eligrey.com | |
| * Public Domain. | |
| * NO WARRANTY EXPRESSED OR IMPLIED. USE AT YOUR OWN RISK. | |
| */ |
In this document I am using Sass's SCSS syntax. You can choose to use the indented syntax in sass, if you prefer it, it has no functional differences from the SCSS syntax.
For Less, I'm using the JavaScript version because this is what they suggest on the website. The ruby version may be different.
| /** | |
| * Basic LessCSS Build System for Sublime Text 2 | |
| * | |
| * Prerequisites: node.js, global lesscss node module | |
| * How it works: | |
| * 1. Create the folders "src/css" and "assets/css" in your project root | |
| * 2. Put all your .less files into "src/css" | |
| * 3. Open your main .less file and hit "Build" | |
| * 4. Dance happily around your minified and compiled CSS file in "assets/css" | |
| * 5. Profit |
| // This method gives you an easier way of calling super | |
| // when you're using Backbone in plain javascript. | |
| // It lets you avoid writing the constructor's name multiple | |
| // times. You still have to specify the name of the method. | |
| // | |
| // So instead of having to write: | |
| // | |
| // User = Backbone.Model.extend({ | |
| // save: function(attrs) { | |
| // this.beforeSave(attrs); |
| var TableViewRow = Backbone.View.extend({ | |
| tagName: "tr", | |
| template: _.template("<td><%= firstName %></td><td><%= lastName %></td>"), | |
| render: function() { | |
| this.$el.html(this.template(this.model.toJSON())); | |
| return this; | |
| } | |
| }); |
| class Example.Views.Table extends Backbone.View | |
| template: JST['example/table'] | |
| initialize: -> | |
| @collection.on 'add', @addOne | |
| render: -> | |
| @$el.html @template() | |
| @addAll() | |
| @ |
by Dale Sande
CSS has had a long and sordid past. A developer never sets out with the goal of making a complete and total mess of things. Their intention is not to build something that is practically illegible, impractical to maintain and is limited in scale. But somehow, this is where many inevitably end up. Luckily, all is not lost. With some simple strategies, organizational methods and out-of-the box tools, we can really help get that junk-drawer inline.
For many of us getting started with Sass, at one time or another have created a junk-drawer of files. For most, this was a rookie mistake, but for others, this is a continuing issue with our architecture and file management techniques. Sass doesn't come with any real rules for file management so developers are pretty much left to their own devices.
CSS started out with very simple intentions, but as [tableless web design][1.1] began to really take a foothold, o
A lot of times you are developing a web application on your own laptop or home computer and would like to demo it to the public. Most of those times you are behind a router/firewall and you don't have a public IP address. Instead of configuring routers (often not possible), this solution gives you a public URL that's reverse tunnelled via ssh to your laptop.
Because of the relaxation of the sshd setup, it's best used on a dedicated virtual machine just for this (an Amazon micro instance for example).
| module.exports = function(grunt) { | |
| grunt.initConfig({ | |
| pkg: grunt.file.readJSON('package.json'), | |
| shell: { | |
| jekyllBuild: { | |
| command: 'jekyll build' | |
| }, | |
| jekyllServe: { | |
| command: 'jekyll serve' | |
| } |
