RubyGems - gigantron - Versions diffs - 0.1.1 → 0.1.2 - Mend

gigantron 0.1.1 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (62) hide show

data/test/test_generator_helper.rb +29 -29
data/test/test_gigantron_generator.rb +118 -114
data/test/test_helper.rb +4 -4
data/test/test_mapreduce_task_generator.rb +50 -50
data/test/test_migration_generator.rb +49 -49
data/test/test_model_generator.rb +53 -53
data/test/test_task_generator.rb +48 -48
metadata +48 -109
data/History.txt +0 -15
data/License.txt +0 -20
data/Manifest.txt +0 -62
data/PostInstall.txt +0 -4
data/README.txt +0 -77
data/Rakefile +0 -4
data/app_generators/gigantron/USAGE +0 -7
data/app_generators/gigantron/gigantron_generator.rb +0 -81
data/app_generators/gigantron/templates/Rakefile +0 -12
data/app_generators/gigantron/templates/database.yml +0 -8
data/app_generators/gigantron/templates/initialize.rb +0 -34
data/app_generators/gigantron/templates/tasks/import.rake +0 -10
data/app_generators/gigantron/templates/test/tasks/test_import.rb +0 -23
data/app_generators/gigantron/templates/test/test_helper.rb +0 -7
data/bin/gigantron +0 -15
data/config/hoe.rb +0 -82
data/config/requirements.rb +0 -15
data/gigantron_generators/mapreduce_task/USAGE +0 -5
data/gigantron_generators/mapreduce_task/mapreduce_task_generator.rb +0 -54
data/gigantron_generators/mapreduce_task/templates/mapreduce/mr_task.rb +0 -22
data/gigantron_generators/mapreduce_task/templates/tasks/task.rake +0 -5
data/gigantron_generators/mapreduce_task/templates/test/tasks/test_task.rb +0 -22
data/gigantron_generators/migration/USAGE +0 -5
data/gigantron_generators/migration/migration_generator.rb +0 -61
data/gigantron_generators/migration/templates/db/migrate/migration.rb +0 -7
data/gigantron_generators/model/USAGE +0 -11
data/gigantron_generators/model/model_generator.rb +0 -54
data/gigantron_generators/model/templates/models/model.rb +0 -3
data/gigantron_generators/model/templates/test/models/test_model.rb +0 -13
data/gigantron_generators/task/USAGE +0 -10
data/gigantron_generators/task/task_generator.rb +0 -51
data/gigantron_generators/task/templates/tasks/task.rake +0 -4
data/gigantron_generators/task/templates/test/tasks/test_task.rb +0 -22
data/lib/gigantron/migrator.rb +0 -10
data/lib/gigantron/tasks/db.rb +0 -11
data/lib/gigantron/tasks/test.rb +0 -30
data/lib/gigantron/version.rb +0 -9
data/lib/gigantron.rb +0 -0
data/script/console +0 -10
data/script/destroy +0 -14
data/script/generate +0 -14
data/script/txt2html +0 -82
data/setup.rb +0 -1585
data/tasks/deployment.rake +0 -34
data/tasks/environment.rake +0 -7
data/tasks/website.rake +0 -17
data/test/template_database.yml +0 -9
data/test/template_database.yml.example +0 -9
data/test/template_migration.rb +0 -16
data/website/index.html +0 -213
data/website/index.txt +0 -145
data/website/javascripts/rounded_corners_lite.inc.js +0 -285
data/website/stylesheets/screen.css +0 -138
data/website/template.html.erb +0 -48

data/tasks/deployment.rake DELETED Viewed

@@ -1,34 +0,0 @@
-desc 'Release the website and new gem version'
-task :deploy => [:check_version, :website, :release] do
-  puts "Remember to create SVN tag:"
-  puts "svn copy svn+ssh://#{rubyforge_username}@rubyforge.org/var/svn/#{PATH}/trunk " +
-    "svn+ssh://#{rubyforge_username}@rubyforge.org/var/svn/#{PATH}/tags/REL-#{VERS} "
-  puts "Suggested comment:"
-  puts "Tagging release #{CHANGES}"
-end
-desc 'Runs tasks website_generate and install_gem as a local deployment of the gem'
-task :local_deploy => [:website_generate, :install_gem]
-task :check_version do
-  unless ENV['VERSION']
-    puts 'Must pass a VERSION=x.y.z release version'
-    exit
-  end
-  unless ENV['VERSION'] == VERS
-    puts "Please update your version.rb to match the release version, currently #{VERS}"
-    exit
-  end
-end
-desc 'Install the package as a gem, without generating documentation(ri/rdoc)'
-task :install_gem_no_doc => [:clean, :package] do
-  sh "#{'sudo ' unless Hoe::WINDOZE }gem install pkg/*.gem --no-rdoc --no-ri"
-end
-namespace :manifest do
-  desc 'Recreate Manifest.txt to include ALL files'
-  task :refresh do
-    `rake check_manifest | patch -p0 > Manifest.txt`
-  end
-end

data/tasks/environment.rake DELETED Viewed

@@ -1,7 +0,0 @@
-task :ruby_env do
-  RUBY_APP = if RUBY_PLATFORM =~ /java/
-    "jruby"
-  else
-    "ruby"
-  end unless defined? RUBY_APP
-end

data/tasks/website.rake DELETED Viewed

@@ -1,17 +0,0 @@
-desc 'Generate website files'
-task :website_generate => :ruby_env do
-  (Dir['website/**/*.txt'] - Dir['website/version*.txt']).each do |txt|
-    sh %{ #{RUBY_APP} script/txt2html #{txt} > #{txt.gsub(/txt$/,'html')} }
-  end
-end
-desc 'Upload website files to rubyforge'
-task :website_upload do
-  host = "#{rubyforge_username}@rubyforge.org"
-  remote_dir = "/var/www/gforge-projects/#{PATH}/"
-  local_dir = 'website'
-  sh %{rsync -aCv #{local_dir}/ #{host}:#{remote_dir}}
-end
-desc 'Generate and upload website files'
-task :website => [:website_generate, :website_upload, :publish_docs]

data/test/template_database.yml DELETED Viewed

@@ -1,9 +0,0 @@
-# JRuby
-:test:
-  :adapter: jdbcsqlite3
-  :url: jdbc:sqlite:<%= GTRON_ROOT %>/db/test.sqlite3
-# Ruby 1.8
-#:test:
-#  :adapter: sqlite3
-#  :database: <%= File.expand_path GTRON_ROOT %>/db/test.sqlite3

data/test/template_database.yml.example DELETED Viewed

@@ -1,9 +0,0 @@
-# JRuby
-#:test:
-#  :adapter: jdbcsqlite3
-#  :url: jdbc:sqlite:<%= GTRON_ROOT %>/db/test.sqlite3
-# Ruby 1.8
-#:test:
-#  :adapter: sqlite3
-#  :database: <%= File.expand_path GTRON_ROOT %>/db/test.sqlite3

data/test/template_migration.rb DELETED Viewed

@@ -1,16 +0,0 @@
-class CreateFoos < ActiveRecord::Migration
-  def self.up
-    create_table :foos do |t|
-      t.string :title
-    end
-    %w(Foo Bar).each do |t|
-      Foo.new(:title => t).save
-    end
-  end
-  def self.down
-    drop_table :foos
-  end
-end

data/website/index.html DELETED Viewed

@@ -1,213 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
-"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
-<head>
-  <link rel="stylesheet" href="stylesheets/screen.css" type="text/css" media="screen" />
-  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-  <title>
-      Gigantron: Processor of Data
-  </title>
-  <script src="javascripts/rounded_corners_lite.inc.js" type="text/javascript"></script>
-<style>
-</style>
-  <script type="text/javascript">
-    window.onload = function() {
-      settings = {
-          tl: { radius: 10 },
-          tr: { radius: 10 },
-          bl: { radius: 10 },
-          br: { radius: 10 },
-          antiAlias: true,
-          autoPad: true,
-          validTags: ["div"]
-      }
-      var versionBox = new curvyCorners(settings, document.getElementById("version"));
-      versionBox.applyCornersToAll();
-    }
-  </script>
-</head>
-<body>
-<div id="main">
-    <h1>Gigantron: Processor of Data</h1>
-    <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/gigantron"; return false'>
-      <p>Get Version</p>
-      <a href="http://rubyforge.org/projects/gigantron" class="numbers">0.1.1</a>
-    </div>
-    <h1>&#x2192; &#8216;gigantron&#8217;</h1>
-	<h2>What</h2>
-	<p>Gigantron is a simple framework for the creation and organization of
-data processing projects. Data-processing transforms are created as Rake tasks
-and data is handled through ActiveRecord models. (DataMapper was the original
-plan, but it has problems playing nicely with JRuby for now).</p>
-	<p>Ruby is great for exploratory data processing.  Data processing projects tend
-to grow up and encompass large numbers of random scripts and input files.  It
-is easy to get lost in coding and lose organization.  Gigantron is an attempt
-to use code generation and random magic to make maintaining organized DP
-projects simple.  Code is separated into data (models) and operations on the
-data (tasks).  Code generators stub out these files and the associated tests
-for the user.</p>
-	<p>Gigantron was written for my own needs working with atmospheric data and will
-evolve through use to reduce the trivialities that can sometimes dominate the
-work of developers.</p>
-	<h2>Installing</h2>
-	<p><pre class='syntax'><span class="ident">sudo</span> <span class="ident">gem</span> <span class="ident">install</span> <span class="ident">gigantron</span></pre></p>
-	<h2>The basics</h2>
-<pre>
-# Generate new project
-shell&gt; $ gigantron project
-      create
-      create  tasks
-      create  db
-      create  models
-      create  lib
-      create  test
-      create  Rakefile
-      create  database.yml
-      create  initialize.rb
-      create  tasks/import.rake
-      create  test/test_helper.rb
-      create  test/models
-      create  test/tasks
-      create  test/tasks/test_import.rb
-  dependency  install_rubigen_scripts
-      create    script
-      create    script/generate
-      create    script/destroy
-shell&gt; $ cd project
-# Create new model
-shell&gt; $ script/generate model modis
-      exists  models/
-      create  models/modis.rb
-      exists  test/
-      exists  test/models/
-      create  test/models/test_modis.rb
-shell&gt; $ script/generate task modis_to_kml
-      exists  tasks/
-      create  tasks/modis_to_kml.rake
-      exists  test/
-      exists  test/tasks/
-      create  test/tasks/test_modis_to_kml.rb
-</pre>
-	<p>One can edit these files to add functionality.  Gigantron by default includes
-ActiveSupport for convenience.</p>
-	<h2>Hacking</h2>
-	<p>Gigantron is super minimal now, so modifying it is pretty easy.  The gigantron
-application generator (that which is invoked by the <code>gigantron</code> command) lives
-in <code>app_generators/gigantron/</code>.  The template files and the template dir
-structure are in <code>app_generators/gigantron/templates/</code>.  When adding new
-templates, directories, or files, add the names first to the tests in
-<code>test/test_gigantron_generator.rb</code>, then the stubs to
-<code>app_generators/gigantron/templates</code>, and then finally describe them in the
-manifest section of <code>app_generators/gigantron/gigantron_generator.rb</code>.  It
-should look something like</p>
-	<p><pre class='syntax'>
-  <span class="keyword">def </span><span class="method">manifest</span>
-    <span class="ident">record</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">m</span><span class="punct">|</span>
-      <span class="punct">...</span>
-      <span class="ident">m</span><span class="punct">.</span><span class="ident">file</span> <span class="punct">&quot;</span><span class="string">new_file</span><span class="punct">&quot;,</span> <span class="punct">&quot;</span><span class="string">new_file</span><span class="punct">&quot;</span> <span class="comment">#straight file copy</span>
-      <span class="ident">m</span><span class="punct">.</span><span class="ident">directory</span> <span class="punct">&quot;</span><span class="string">my_new_dir</span><span class="punct">&quot;</span> <span class="comment">#create directory</span>
-      <span class="ident">m</span><span class="punct">.</span><span class="ident">template</span> <span class="punct">&quot;</span><span class="string">new_thing</span><span class="punct">&quot;,</span> <span class="punct">&quot;</span><span class="string">new_thing</span><span class="punct">&quot;</span> <span class="comment">#runs file through ERB when copying</span>
-    <span class="keyword">end</span>
-  <span class="keyword">end</span>
-</pre></p>
-	<p>It might be handy to know that in <code>gigantron_generator.rb</code> the name provided to the generator can be referenced as <code>@name</code>.  This can be used like</p>
-	<p><pre class='syntax'>
-<span class="ident">record</span> <span class="keyword">do</span> <span class="punct">|</span><span class="ident">m</span><span class="punct">|</span>
-  <span class="ident">m</span><span class="punct">.</span><span class="ident">file</span> <span class="punct">&quot;</span><span class="string">renamed_file</span><span class="punct">&quot;,</span> <span class="punct">&quot;</span><span class="string"><span class="expr">#{@name}</span>_file</span><span class="punct">&quot;</span>
-<span class="keyword">end</span>
-</pre></p>
-	<p>The same value is available to your templates as just <code>name</code>.  You can template
-a file like</p>
-	<p><pre class='syntax'>
-<span class="keyword">class </span><span class="class">Test</span><span class="punct">&lt;%=</span><span class="string"> name.camelcase %&gt; &lt; Test::Unit::TestCase
-  ...
-end<span class="normal">
-</span></span></pre></p>
-	<p>The same process applies to the model and task generator for gigantron
-projects.  These generators live in <code>gigantron_generators/</code>.  Modifying them
-is exactly the same as modifying the application generator.</p>
-	<p>All of this is pretty vanilla <a href="http://rubigen.rubyforge.org">RubiGen</a>, so if in doubt, check out the docos on that fine piece of work.</p>
-	<p>The only other place for code in Gigantron is is <code>lib/gigantron/tasks/</code> where a few boilerplate test and db tasks live.  I think I ripped the test tasks off of rails.</p>
-	<p>If you have any questions, do contact me.  I am interested in anything that will make Gigantron suck less and be useful to people.</p>
-	<h2>How to submit patches</h2>
-	<ul>
-	<li>github: <a href="http://github.com/schleyfox/gigantron/tree/master">http://github.com/schleyfox/gigantron/tree/master</a></li>
-	</ul>
-<pre>git clone git://github.com/schleyfox/gigantron.git</pre>
-	<h3>Build and test instructions</h3>
-<pre>cd gigantron
-cp test/template_database.yml.example test/template_database.yml
-vim test/template_database.yml
-rake test
-rake install_gem</pre>
-	<h2>License</h2>
-	<p>This code is free to use under the terms of the <span class="caps">MIT</span> license.</p>
-	<h2>Contact</h2>
-	<p>Comments are welcome. Send an email to <a href="mailto:ben@pixelmachine.org">Ben Hughes</a></p>
-    <p class="coda">
-      <a href="ben@pixelmachine.org">Ben Hughes</a>, 19th June 2008<br>
-      Theme extended from <a href="http://rb2js.rubyforge.org/">Paul Battley</a>
-    </p>
-</div>
-<!-- insert site tracking codes here, like Google Urchin -->
-</body>
-</html>

data/website/index.txt DELETED Viewed

@@ -1,145 +0,0 @@
-h1. Gigantron: Processor of Data
-h1. &#x2192; 'gigantron'
-h2. What
-Gigantron is a simple framework for the creation and organization of
-data processing projects. Data-processing transforms are created as Rake tasks
-and data is handled through ActiveRecord models. (DataMapper was the original
-plan, but it has problems playing nicely with JRuby for now).
-Ruby is great for exploratory data processing.  Data processing projects tend
-to grow up and encompass large numbers of random scripts and input files.  It
-is easy to get lost in coding and lose organization.  Gigantron is an attempt
-to use code generation and random magic to make maintaining organized DP
-projects simple.  Code is separated into data (models) and operations on the
-data (tasks).  Code generators stub out these files and the associated tests
-for the user.
-Gigantron was written for my own needs working with atmospheric data and will
-evolve through use to reduce the trivialities that can sometimes dominate the
-work of developers.
-h2. Installing
-<pre syntax="ruby">sudo gem install gigantron</pre>
-h2. The basics
-<pre>
-# Generate new project
-shell> $ gigantron project
-      create
-      create  tasks
-      create  db
-      create  models
-      create  lib
-      create  test
-      create  Rakefile
-      create  database.yml
-      create  initialize.rb
-      create  tasks/import.rake
-      create  test/test_helper.rb
-      create  test/models
-      create  test/tasks
-      create  test/tasks/test_import.rb
-  dependency  install_rubigen_scripts
-      create    script
-      create    script/generate
-      create    script/destroy
-shell> $ cd project
-# Create new model
-shell> $ script/generate model modis
-      exists  models/
-      create  models/modis.rb
-      exists  test/
-      exists  test/models/
-      create  test/models/test_modis.rb
-shell> $ script/generate task modis_to_kml
-      exists  tasks/
-      create  tasks/modis_to_kml.rake
-      exists  test/
-      exists  test/tasks/
-      create  test/tasks/test_modis_to_kml.rb
-</pre>
-One can edit these files to add functionality.  Gigantron by default includes
-ActiveSupport for convenience.
-h2. Hacking
-Gigantron is super minimal now, so modifying it is pretty easy.  The gigantron
-application generator (that which is invoked by the @gigantron@ command) lives
-in @app_generators/gigantron/@.  The template files and the template dir
-structure are in @app_generators/gigantron/templates/@.  When adding new
-templates, directories, or files, add the names first to the tests in
-@test/test_gigantron_generator.rb@, then the stubs to
-@app_generators/gigantron/templates@, and then finally describe them in the
-manifest section of @app_generators/gigantron/gigantron_generator.rb@.  It
-should look something like
-<pre syntax="ruby">
-  def manifest
-    record do |m|
-      ...
-      m.file "new_file", "new_file" #straight file copy
-      m.directory "my_new_dir" #create directory
-      m.template "new_thing", "new_thing" #runs file through ERB when copying
-    end
-  end
-</pre>
-It might be handy to know that in @gigantron_generator.rb@ the name provided to the generator can be referenced as @@name@.  This can be used like
-<pre syntax="ruby">
-record do |m|
-  m.file "renamed_file", "#{@name}_file"
-end
-</pre>
-The same value is available to your templates as just @name@.  You can template
-a file like
-<pre syntax="ruby">
-class Test<%%= name.camelcase %> < Test::Unit::TestCase
-  ...
-end
-</pre>
-The same process applies to the model and task generator for gigantron
-projects.  These generators live in @gigantron_generators/@.  Modifying them
-is exactly the same as modifying the application generator.
-All of this is pretty vanilla "RubiGen":http://rubigen.rubyforge.org, so if in doubt, check out the docos on that fine piece of work.
-The only other place for code in Gigantron is is @lib/gigantron/tasks/@ where a few boilerplate test and db tasks live.  I think I ripped the test tasks off of rails.
-If you have any questions, do contact me.  I am interested in anything that will make Gigantron suck less and be useful to people.
-h2. How to submit patches
-* github: "http://github.com/schleyfox/gigantron/tree/master":http://github.com/schleyfox/gigantron/tree/master
-<pre>git clone git://github.com/schleyfox/gigantron.git</pre>
-h3. Build and test instructions
-<pre>cd gigantron
-cp test/template_database.yml.example test/template_database.yml
-vim test/template_database.yml
-rake test
-rake install_gem</pre>
-h2. License
-This code is free to use under the terms of the MIT license.
-h2. Contact
-Comments are welcome. Send an email to "Ben Hughes":mailto:ben@pixelmachine.org