| // jquery invert plugin | |
| // by paul irish | |
| // some (bad) code from this css color inverter | |
| // http://plugins.jquery.com/project/invert-color | |
| // some better code via Opera to inverse images via canvas | |
| // http://dev.opera.com/articles/view/html-5-canvas-the-basics/#insertingimages | |
| // and some imagesLoaded stuff from me | |
| // http://gist.github.com/268257 |
| The MIT License (MIT) | |
| Copyright (c) James Dennes | |
| Permission is hereby granted, free of charge, to any person obtaining a copy | |
| of this software and associated documentation files (the "Software"), to deal | |
| in the Software without restriction, including without limitation the rights | |
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | |
| copies of the Software, and to permit persons to whom the Software is | |
| furnished to do so, subject to the following conditions: |
| <?php | |
| /** | |
| * Premailer API PHP class | |
| * Premailer is a library/service for making HTML more palatable for various inept email clients, in particular GMail | |
| * Primary function is to convert style tags into equivalent inline styles so styling can survive <head> tag removal | |
| * Premailer is owned by Dialect Communications group | |
| * @link http://premailer.dialect.ca/api | |
| * @author Marcus Bointon <marcus@synchromedia.co.uk> | |
| */ | |
| <!-- | |
| Progressive Disclosure Demo - Updated 15 August, 2012 by Ros | |
| Thank you for taking a look under the hood of our progressive disclosure demo. Please note that this is a work in progress, so it's a tad messy and bound to change. | |
| If you have any questions, feel free to pop a line to support@campaignmonitor.com - we might learn something, too! | |
| Known bugs | |
| ---------- |
| # This is a template .gitignore file for git-managed WordPress projects. | |
| # | |
| # Fact: you don't want WordPress core files, or your server-specific | |
| # configuration files etc., in your project's repository. You just don't. | |
| # | |
| # Solution: stick this file up your repository root (which it assumes is | |
| # also the WordPress root directory) and add exceptions for any plugins, | |
| # themes, and other directories that should be under version control. | |
| # | |
| # See the comments below for more info on how to add exceptions for your |
| Sublime Text Plugins iCloud Drive | |
| First Machine | |
| On your first machine, use the following instructions. | |
| $ cd ~/Library/Application\ Support/Sublime\ Text\ 2/Packages/ | |
| $ mkdir ~/Library/Mobile\ Documents/com\~apple\~CloudDocs/Web\ Dev/Plugins | |
| $ mv User ~/Library/Mobile\ Documents/com\~apple\~CloudDocs/Web\ Dev/Plugins | |
| $ ln -s ~/Library/Mobile\ Documents/com\~apple\~CloudDocs/Web\ Dev/Plugins/User |
| function ConvertGoogleDocToCleanHtml() { | |
| var body = DocumentApp.getActiveDocument()//.getBody(); | |
| var numChildren = body.getNumChildren(); | |
| var output = []; | |
| var images = []; | |
| var listCounters = {}; | |
| var toc = {} | |
| for (var i = 0; i < numChildren; i++) { | |
| var p = body.getChild(i); |
As a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.
Easy example on how to put marker on a d3.js map.
You got 2 options:
The strength of Sass is the mixins and functions. Being able to automate many of the repetitive coding for CSS is both amazing in building and maintaining a clean and efficient code. I often find many developers creating complex systems for simple tasks, such as managing a font stack. This can be tedious to set up and employ. In this article, I will explain how I automate this system.
The font stack is one of those problems which are often solved by simple variables. In this instance, it makes a lot of sense and is easy enough to work with. But when you work with our (beloved) designers from Dogstudio, you can be sure of having to use lot of font variants. It quickly happens that I do not remember all the properties of each variants. And when I say "use lot of font variants", I mean at least 15 in most cases.
Instead of simply define variables, I will ceate a font stack map and a mixin to use the map easily.
