pixelistik pixelistik

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

IE 7/8/9/10/11 Virtual machines from Microsoft

We have moved: https://github.com/magnetikonline/linuxmicrosoftievirtualmachines

Due to the popularity of this Gist, and the work in keeping it updated via a Gist, all future updates will take place at the above location. Thanks!

When you do your first Sonar run on your project, you get a lot of new quality numbers to play with, but no trends. You only have one data set for comparison, the now picture.

Wouldn't it be nice if you could see the current trend of the project without waiting a couple of month for the 'daily/weekly' Sonar runs to fill up the data? Well, you're in luck! And if you're using git as a version system as well, this is your day. :)

In the Sonar Advanced Parameter documentation you will find a System Property called sonar.projectDate. The property let you tell Sonar when in time the running analysis was ran.

By combining this property and what your version system does best, track changes to source, we can now play back the history of the project as far as Sonar is concerned.

This little Bash script illustrates the concept. To spell out what it does in human readable form:

	#![feature(lang_items)]
	#![no_std]

	#[no_mangle]
	pub fn add_one(x: i32) -> i32 {
	x + 1
	}


	// needed for no_std

	# -- coding:utf-8 --
	from __future__ import absolute_import
	from __future__ import unicode_literals
	from __future__ import print_function

	import json
	import uuid
	import time
	import gevent

	# Hello, and welcome to makefile basics.
	#
	# You will learn why `make` is so great, and why, despite its "weird" syntax,
	# it is actually a highly expressive, efficient, and powerful way to build
	# programs.
	#
	# Once you're done here, go to
	# http://www.gnu.org/software/make/manual/make.html
	# to learn SOOOO much more.

	void function() {//closure

	var global = this
	, _initKeyboardEvent_type = (function( e ) {
	try {
	e.initKeyboardEvent(
	"keyup" // in DOMString typeArg
	, false // in boolean canBubbleArg
	, false // in boolean cancelableArg
	, global // in views::AbstractView viewArg

	Assuming the base URL to be this (need to edit to fit yours):

	http://cqauthor1.company.com:4502

	SEARCH

	Search UI:

	/crx/explorer/ui/search.jsp?Path=&Query=

	function sendError(message, url, lineNum) {
	var i;

	// First check the URL and line number of the error
	url = url \|\| window.location.href;
	lineNum = lineNum \|\| 'None';

	// If the error is from these 3rd party script URLs, we ignore
	// We could also just ignore errors from all scripts that aren't our own
	var scriptURLs = [

	#Refer: http://www.linuxfoundation.org/collaborate/workgroups/networking/netem#Delaying_only_some_traffic
	#Refer: http://www.bomisofmab.com/blog/?p=100
	#Refer: http://drija.com/linux/41983/simulating-a-low-bandwidth-high-latency-network-connection-on-linux/
	#Setup the rate control and delay
	sudo tc qdisc add dev lo root handle 1: htb default 12
	sudo tc class add dev lo parent 1:1 classid 1:12 htb rate 56kbps ceil 128kbps
	sudo tc qdisc add dev lo parent 1:12 netem delay 200ms

	#Remove the rate control/delay
	sudo tc qdisc del dev lo root