= Flippa CSS Styleguide =
== CRITICAL: Regenerating Stylesheets for deployment ==
If you edit any stylesheets in app/stylesheets, you must run the following command from the project's root:
$> bundle exec compass compile
== Basic Formatting ==
= Flippa CSS Styleguide =
== CRITICAL: Regenerating Stylesheets for deployment ==
If you edit any stylesheets in app/stylesheets, you must run the following command from the project's root:
$> bundle exec compass compile
== Basic Formatting ==
# =========== lib file =================== | |
class XssScrubber | |
def angular_xss_filter(unknown) | |
case unknown | |
when Hash | |
angular_xss_filter_hash(unknown) | |
when Array | |
angular_xss_filter_array(unknown) | |
when String |
// scheduling supports all formats offered by later.js (http://bunkat.github.io/later/) | |
// Scheduled device event | |
schedule('blinds', 'open').at('10:00am').execute(); | |
schedule('blinds', 'closed').at('5:00pm').execute(); | |
// Scheduled compensation triggers | |
every('5 minutes') | |
.if(env.tooHot | |
.respond(turnOnFans) |
Firstly thank you. FireReady and the emergency.vic site are an incredible resource, especially yesterday sitting here in the Macedon Ranges watching events unfold in Gisborne and considering when and where we might evacuate. So to everyone involved, thank you and congratulations on delivering a rock-solid resource.
A couple of notes on the site and why I pointed people to the text version...
While the server response has remained fast, that's only the start of the loading as the JS fires and brings in all the map tiles etc. Right now over my iinet ADSL1 connection 1.2km from the centre of Kyneton (Telstra infastructure), the page response has finished in 786ms, but the page takes 15.07 seconds to finish loading resources, the last of which are all the map tiles. Most of these map tiles are pre-loads by Google, with all the tiles in view finishing within 7 seconds. 90 requests in total. The memory heap for this page was 43.8mb (Chrome 32, OSX)
I hereby claim:
To claim this, I am signing this object:
.PHONY: setup test | |
setup: | |
mkdir test | |
mkdir test/specs | |
mkdir test/fixtures | |
mkdir assets | |
mkdir assets/js | |
mkdir assets/css | |
mv test-main.js ./test/ |
- I wrote this on the train after a long day with a heavy head cold. I haven't run it, | |
but regardless of likely errors I think it expresses the design well enough. | |
- Segment and ConditionSet look close to identical, but that's likely due to the simplified | |
nature of the outline you provided | |
- I don't like attaching components to classes unless they're `js-`, as it's coupling | |
your styling and behaviour layers. We excelusively use data attributes for JS-DOM coupling | |
and I've quickly grown fond of the approach. |
# watch assets for changes in development, using bower deps | |
watch: | |
sass -I assets/scss -I bower_components --watch assets/scss:public/css | |
# watch assets for changes in development, using npm deps | |
watch: | |
sass $(foreach d, $(shell find . -name 'node_modules' -type d), -I$d) -I assets/scss --watch assets/scss:public/css | |
# and what does that `find` call look like in reality? |
define(function(require) { | |
'use strict'; | |
var defineComponent = require('flight/lib/component'); | |
return defineComponent(ComponentRegistry); | |
function ComponentRegistry() { | |
this.components = []; | |
this.defaultAttrs({ |
#!/bin/sh | |
# Convert movie (screencast) to lofi animated gif for embedding in github PR's, emails etc. | |
# | |
# Requires: ffmpeg, gifsicle | |
# Screencasts are easily captured in Quicktime Player: File > New screen recording | |
if [ -z "$1" ] | |
then | |
echo "Usage: mov2gif input.mov 700 > output.gif" |