nvd3-rails 0.0.1

data/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "vendor/assets/javascripts/nvd3"]
+	path = vendor/assets/javascripts/nvd3
+	url = git://github.com/adeven/nvd3.git

data/README.md

@@ -0,0 +1,101 @@
+# NVD3 Rails - reusable charts for rails 3
+
+## Install
+
+To include nvd3-rails into your rails project add
+
+    gem "nvd3-rails", :git => "git@github.com:adeven/nvd3-rails.git", :submodules => true
+
+To your Projects Gemfile.
+
+To add the necessary javascript files into your asset pipeline add
+
+    //= require nvd3-rails
+
+in ```app/assets/javascripts/application.js```
+
+also add
+
+    *= require nvd3-rails
+
+in ```app/assets/stylesheets/application.css```
+
+Note as of today nvd3 clutters the model naming e.g. lineWithFisheyeChart.js and lineChart.js export their model both as lineChart.
+If you only need a subset of models e.g. lineChart you can add 
+
+    //= require nvd3/lib/d3.v2
+    //= require nvd3/src/core
+    //= require nvd3/src/tooltip
+    //= require nvd3/src/utils.js
+    //= require nvd3/src/models/lineChart
+    //= require nvd3/src/models/legend.js
+    //= require nvd3/src/models/axis.js
+    //= require nvd3/src/models/scatter.js
+    //= require nvd3/src/models/line.js
+
+to your ```application.js```
+
+## Contribution Guide
+
+### Updating Submodules
+
+The repository uses submodules following are the steps to manually get the submodules:
+
+    git clone https://github.com/adeven/nvd3-rails.git
+    cd nvd3-rails
+    git submodule init
+    git submodule update
+
+Or:
+
+    git clone https://github.com/adeven/nvd3-rails.git
+    cd nvd3-rails
+    git submodule update --init
+
+Or:
+
+    git clone --recursive https://github.com/adeven/nvd3-rails.git
+    cd nvd3-rails
+
+
+If you want to work inside a submodule, it is possible, but first you need to checkout a branch:
+
+    cd vendor/assets/javascripts/nvd3
+    git checkout master
+
+After you've committed your changes to the submodule, you'll update the nvd3-rails project to point to the new commit, but remember to push the submodule changes before pushing the new nvd3-rails commit:
+
+    cd vendor/assets/javascripts/nvd3
+    git push origin master
+    cd ..
+    git add vendor/assets/javascripts/nvd3
+    git commit
+
+### cleaning
+
+If you want to purge your working directory back to the status of upstream, following commands can be used (remember everything you've worked on is gone after these):
+
+git reset --hard upstream/master
+git clean -fdx
+
+### Using a local copy during development
+
+Nvd3-rails gets added as a Rails::Engine to your project.
+
+Generally during development you want your main application to include a local development copy of your engine.
+You should be able to add gem groups for each Rails environment to your Gemfile, like this:
+
+```ruby
+group :development do
+    gem "nvd3-rails", :path => "../nvd3-rails"
+end
+
+group :production do
+    gem "nvd3-rails", :git => "git://github.com/adeven/nvd3-rails.git"
+end
+```
+
+In Bundler 1.1 and earlier, that generates this error message: "You cannot specify the same gem twice coming from different sources."
+This should be fixed in 1.2 https://github.com/carlhuda/bundler/issues/751
+
+There are several work arounds for this, however I sugest to update to the latest version of bundle.

data/lib/nvd3-rails.rb

@@ -0,0 +1 @@
+require 'nvd3/rails'

data/lib/nvd3/rails.rb

@@ -0,0 +1,8 @@
+require 'nvd3/rails/engine'
+require 'nvd3/rails/version'
+
+module NVD3
+  module Rails
+
+  end
+end

data/lib/nvd3/rails/engine.rb

@@ -0,0 +1,6 @@
+module NVD3
+  module Rails
+    class Engine < ::Rails::Engine
+    end
+  end
+end

data/lib/nvd3/rails/version.rb

@@ -0,0 +1,5 @@
+module NVD3
+  module Rails
+    VERSION = "0.0.1"
+  end
+end

data/nvd3-rails.gemspec

@@ -0,0 +1,21 @@
+# -*- encoding: utf-8 -*-
+require File.expand_path('../lib/nvd3/rails/version', __FILE__)
+
+Gem::Specification.new do |s|
+  s.name        = "nvd3-rails"
+  s.version     = NVD3::Rails::VERSION
+  s.platform    = Gem::Platform::RUBY
+  s.authors     = ["Manuel Knie"]
+  s.email       = ["manuel@adeven.com"]
+  s.homepage    = "http://adeven.com"
+  s.summary     = "Use nvd3 with Rails 3"
+  s.description = "This gem provides nvd3 for your Rails 3 application."
+
+  s.required_rubygems_version = ">= 1.3.6"
+
+  s.add_dependency "railties", ">= 3.2.0", "< 5.0"
+
+  s.files        = `git ls-files`.split("\n")
+  s.executables  = `git ls-files -- bin/*`.split("\n").map { |f| File.basename(f) }
+  s.require_path = 'lib'
+end

data/vendor/assets/javascripts/nvd3-rails.js

@@ -0,0 +1,7 @@
+//= require ./nvd3/lib/d3.v2
+//= require ./nvd3/lib/fisheye
+//= require ./nvd3/src/core
+//= require ./nvd3/src/tooltip
+//= require ./nvd3/src/utils.js
+//= require_tree ./nvd3/src/models
+//= require set-nvd3-env.js.erb

data/vendor/assets/javascripts/nvd3/.git.sample/HEAD

@@ -0,0 +1 @@
+ref: refs/heads/master

data/vendor/assets/javascripts/nvd3/.git.sample/config

@@ -0,0 +1,13 @@
+[core]
+	repositoryformatversion = 0
+	filemode = true
+	bare = false
+	logallrefupdates = true
+	ignorecase = true
+	precomposeunicode = false
+[remote "origin"]
+	url = git@github.com:NealKemp/nvd3.git
+	fetch = +refs/heads/*:refs/remotes/origin/*
+[branch "master"]
+	remote = origin
+	merge = refs/heads/master

data/vendor/assets/javascripts/nvd3/.git.sample/description

@@ -0,0 +1 @@
+Unnamed repository; edit this file 'description' to name the repository.

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/applypatch-msg.sample

@@ -0,0 +1,15 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message taken by
+# applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.  The hook is
+# allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "applypatch-msg".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/commit-msg" &&
+	exec "$GIT_DIR/hooks/commit-msg" ${1+"$@"}
+:

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/commit-msg.sample

@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message.
+# Called by "git commit" with one argument, the name of the file
+# that has the commit message.  The hook should exit with non-zero
+# status after issuing an appropriate message if it wants to stop the
+# commit.  The hook is allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "commit-msg".
+
+# Uncomment the below to add a Signed-off-by line to the message.
+# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
+# hook is more suited to it.
+#
+# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
+
+# This example catches duplicate Signed-off-by lines.
+
+test "" = "$(grep '^Signed-off-by: ' "$1" |
+	 sort | uniq -c | sed -e '/^[ 	]*1[ 	]/d')" || {
+	echo >&2 Duplicate Signed-off-by lines.
+	exit 1
+}

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/post-update.sample

@@ -0,0 +1,8 @@
+#!/bin/sh
+#
+# An example hook script to prepare a packed repository for use over
+# dumb transports.
+#
+# To enable this hook, rename this file to "post-update".
+
+exec git update-server-info

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/pre-applypatch.sample

@@ -0,0 +1,14 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed
+# by applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-applypatch".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/pre-commit" &&
+	exec "$GIT_DIR/hooks/pre-commit" ${1+"$@"}
+:

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/pre-commit.sample

@@ -0,0 +1,50 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed.
+# Called by "git commit" with no arguments.  The hook should
+# exit with non-zero status after issuing an appropriate message if
+# it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-commit".
+
+if git rev-parse --verify HEAD >/dev/null 2>&1
+then
+	against=HEAD
+else
+	# Initial commit: diff against an empty tree object
+	against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
+fi
+
+# If you want to allow non-ascii filenames set this variable to true.
+allownonascii=$(git config hooks.allownonascii)
+
+# Redirect output to stderr.
+exec 1>&2
+
+# Cross platform projects tend to avoid non-ascii filenames; prevent
+# them from being added to the repository. We exploit the fact that the
+# printable range starts at the space character and ends with tilde.
+if [ "$allownonascii" != "true" ] &&
+	# Note that the use of brackets around a tr range is ok here, (it's
+	# even required, for portability to Solaris 10's /usr/bin/tr), since
+	# the square bracket bytes happen to fall in the designated range.
+	test $(git diff --cached --name-only --diff-filter=A -z $against |
+	  LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
+then
+	echo "Error: Attempt to add a non-ascii file name."
+	echo
+	echo "This can cause problems if you want to work"
+	echo "with people on other platforms."
+	echo
+	echo "To be portable it is advisable to rename the file ..."
+	echo
+	echo "If you know what you are doing you can disable this"
+	echo "check using:"
+	echo
+	echo "  git config hooks.allownonascii true"
+	echo
+	exit 1
+fi
+
+# If there are whitespace errors, print the offending file names and fail.
+exec git diff-index --check --cached $against --

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/pre-push.sample

@@ -0,0 +1,53 @@
+#!/bin/sh
+
+# An example hook script to verify what is about to be pushed.  Called by "git
+# push" after it has checked the remote status, but before anything has been
+# pushed.  If this script exits with a non-zero status nothing will be pushed.
+#
+# This hook is called with the following parameters:
+#
+# $1 -- Name of the remote to which the push is being done
+# $2 -- URL to which the push is being done
+#
+# If pushing without using a named remote those arguments will be equal.
+#
+# Information about the commits which are being pushed is supplied as lines to
+# the standard input in the form:
+#
+#   <local ref> <local sha1> <remote ref> <remote sha1>
+#
+# This sample shows how to prevent push of commits where the log message starts
+# with "WIP" (work in progress).
+
+remote="$1"
+url="$2"
+
+z40=0000000000000000000000000000000000000000
+
+IFS=' '
+while read local_ref local_sha remote_ref remote_sha
+do
+	if [ "$local_sha" = $z40 ]
+	then
+		# Handle delete
+	else
+		if [ "$remote_sha" = $z40 ]
+		then
+			# New branch, examine all commits
+			range="$local_sha"
+		else
+			# Update to existing branch, examine new commits
+			range="$remote_sha..$local_sha"
+		fi
+
+		# Check for WIP commit
+		commit=`git rev-list -n 1 --grep '^WIP' "$range"`
+		if [ -n "$commit" ]
+		then
+			echo "Found WIP commit in $local_ref, not pushing"
+			exit 1
+		fi
+	fi
+done
+
+exit 0

data/vendor/assets/javascripts/nvd3/.git.sample/hooks/pre-rebase.sample

@@ -0,0 +1,169 @@
+#!/bin/sh
+#
+# Copyright (c) 2006, 2008 Junio C Hamano
+#
+# The "pre-rebase" hook is run just before "git rebase" starts doing
+# its job, and can prevent the command from running by exiting with
+# non-zero status.
+#
+# The hook is called with the following parameters:
+#
+# $1 -- the upstream the series was forked from.
+# $2 -- the branch being rebased (or empty when rebasing the current branch).
+#
+# This sample shows how to prevent topic branches that are already
+# merged to 'next' branch from getting rebased, because allowing it
+# would result in rebasing already published history.
+
+publish=next
+basebranch="$1"
+if test "$#" = 2
+then
+	topic="refs/heads/$2"
+else
+	topic=`git symbolic-ref HEAD` ||
+	exit 0 ;# we do not interrupt rebasing detached HEAD
+fi
+
+case "$topic" in
+refs/heads/??/*)
+	;;
+*)
+	exit 0 ;# we do not interrupt others.
+	;;
+esac
+
+# Now we are dealing with a topic branch being rebased
+# on top of master.  Is it OK to rebase it?
+
+# Does the topic really exist?
+git show-ref -q "$topic" || {
+	echo >&2 "No such branch $topic"
+	exit 1
+}
+
+# Is topic fully merged to master?
+not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
+if test -z "$not_in_master"
+then
+	echo >&2 "$topic is fully merged to master; better remove it."
+	exit 1 ;# we could allow it, but there is no point.
+fi
+
+# Is topic ever merged to next?  If so you should not be rebasing it.
+only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
+only_next_2=`git rev-list ^master           ${publish} | sort`
+if test "$only_next_1" = "$only_next_2"
+then
+	not_in_topic=`git rev-list "^$topic" master`
+	if test -z "$not_in_topic"
+	then
+		echo >&2 "$topic is already up-to-date with master"
+		exit 1 ;# we could allow it, but there is no point.
+	else
+		exit 0
+	fi
+else
+	not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
+	/usr/bin/perl -e '
+		my $topic = $ARGV[0];
+		my $msg = "* $topic has commits already merged to public branch:\n";
+		my (%not_in_next) = map {
+			/^([0-9a-f]+) /;
+			($1 => 1);
+		} split(/\n/, $ARGV[1]);
+		for my $elem (map {
+				/^([0-9a-f]+) (.*)$/;
+				[$1 => $2];
+			} split(/\n/, $ARGV[2])) {
+			if (!exists $not_in_next{$elem->[0]}) {
+				if ($msg) {
+					print STDERR $msg;
+					undef $msg;
+				}
+				print STDERR " $elem->[1]\n";
+			}
+		}
+	' "$topic" "$not_in_next" "$not_in_master"
+	exit 1
+fi
+
+exit 0
+
+################################################################
+
+This sample hook safeguards topic branches that have been
+published from being rewound.
+
+The workflow assumed here is:
+
+ * Once a topic branch forks from "master", "master" is never
+   merged into it again (either directly or indirectly).
+
+ * Once a topic branch is fully cooked and merged into "master",
+   it is deleted.  If you need to build on top of it to correct
+   earlier mistakes, a new topic branch is created by forking at
+   the tip of the "master".  This is not strictly necessary, but
+   it makes it easier to keep your history simple.
+
+ * Whenever you need to test or publish your changes to topic
+   branches, merge them into "next" branch.
+
+The script, being an example, hardcodes the publish branch name
+to be "next", but it is trivial to make it configurable via
+$GIT_DIR/config mechanism.
+
+With this workflow, you would want to know:
+
+(1) ... if a topic branch has ever been merged to "next".  Young
+    topic branches can have stupid mistakes you would rather
+    clean up before publishing, and things that have not been
+    merged into other branches can be easily rebased without
+    affecting other people.  But once it is published, you would
+    not want to rewind it.
+
+(2) ... if a topic branch has been fully merged to "master".
+    Then you can delete it.  More importantly, you should not
+    build on top of it -- other people may already want to
+    change things related to the topic as patches against your
+    "master", so if you need further changes, it is better to
+    fork the topic (perhaps with the same name) afresh from the
+    tip of "master".
+
+Let's look at this example:
+
+		   o---o---o---o---o---o---o---o---o---o "next"
+		  /       /           /           /
+		 /   a---a---b A     /           /
+		/   /               /           /
+	       /   /   c---c---c---c B         /
+	      /   /   /             \         /
+	     /   /   /   b---b C     \       /
+	    /   /   /   /             \     /
+    ---o---o---o---o---o---o---o---o---o---o---o "master"
+
+
+A, B and C are topic branches.
+
+ * A has one fix since it was merged up to "next".
+
+ * B has finished.  It has been fully merged up to "master" and "next",
+   and is ready to be deleted.
+
+ * C has not merged to "next" at all.
+
+We would want to allow C to be rebased, refuse A, and encourage
+B to be deleted.
+
+To compute (1):
+
+	git rev-list ^master ^topic next
+	git rev-list ^master        next
+
+	if these match, topic has not merged in next at all.
+
+To compute (2):
+
+	git rev-list master..topic
+
+	if this is empty, it is fully merged to "master".