Most of these guidelines are to match Apple's documentation and community-accepted best practices. Some are derived some personal preference. This document aims to set a standard way of doing things so everyone can do things the same way. If there is something you are not particularly fond of, it is encouraged to do it anyway to be consistent with everyone else.
This document is mainly targeted toward iOS development, but definitely applies to Mac as well.
NSString *foo = @"bar";
| #!/usr/bin/env ruby | |
| require 'rubygems' | |
| require 'json' | |
| unless ARGV.count > 1 | |
| puts "Usage: json_diff.rb json_file_1.json json_file_2.json" | |
| exit | |
| end | |
| def different?(a, b, bi_directional=true) |
The MIT License (MIT)
Copyright (c) 2014 David Underwood
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:
Dashing widget to display a Jenkins build status and build progress
The widget is based on the meter-widget which is default in the Dashing installation
The widget can also see the progress of a "pre-build", i.e if you have a job triggering the actual build you want to define, you can configure this job in the jenkins_build.rb as a prebuild.
For more information, please see Coding Like a tosser
Dashing widget to show the status of builds from CircleCI. Also shows the avatar of the person who is running/breaking/passing the current build.
CIRCLE_CI_AUTH_TOKENhttparty to your Gemfile and run bundle installThen:
Dashing widget to show the build status of a CircleCI project.
CIRCLE_CI_AUTH_TOKENhttparty to your Gemfile and run bundle installThen:
Simple Dashing job to display your Pivotal Tracker stories status.
Dashing widget to display a bunch of current and coming-up Google Calendar events.
The widget shows only one event and is based on the text-widget which is default in the Dashing installation. The time is displayed as human-readable time string with the help of MomentJS.
A Dashing job fetches the events of a given public or private calendar url, orders events to match starting time and sends the data to the dashboard. A certain event offset can be set for each calendar widget so that it will show the first (data-pre="0"), the second (data-pre="1") or any other following event based on the offset. For each calendar you'll have to define a name which enables you to assign custom background colors for events of each calendar.
While the main job is called in larger intervals, there is a second job to be run every minute or so, which kicks out already finished events. In that way processing load
Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].
Today we're looking for:
