richrc 0.0.1 → 0.0.2

data/MIT-LICENSE

@@ -0,0 +1,19 @@
+Copyright (C) 2011 by BigCat a.k.a. miaout17 (miaout17 at gmail dot com)
+
+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:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,33 @@
+# RichRC
+
+RichRC (Rich Rails Console) loads [hirb](https://github.com/cldwalker/hirb) and [wirble](http://pablotron.org/software/wirble/) in rails 3 console without editing files in rails app directory. 
+
+Hirb and wirble are excellent IRB-extension which makes data more readable. In rails 2, we can simply require gems in IRB and start using them. However, In Rails 3, it's needed to add gems into `Gemfile` before using it. Sometimes it doesn't make sense to add IRB-extension gems into rails app Gemfile (Maybe not all developers want hirb and wirble, and it's annoying to add the gems whenever cloning a project). 
+
+Inspired from [xdite's article](http://blog.xdite.net/?p=1839), the extra gems cloud be loaded before `Bundler.setup` is invoked. RichRC mimics the bootstrap process of rails console, loads and initializes extra gems, and starts console normally. 
+
+## Installation
+
+    $ gem install richrc hirb wirble
+
+P.S. In RichRC's gemspec, it doesn't depend on hirb and wirble. If some of the gems are missing, RichRC simply ignore them.
+
+## Running RichRC
+
+    $ cd railsapp
+    $ richrc # instead of `rails console`
+
+That's all :)
+
+The original rails console is not affected. If problems occured with RichRC, you can simply fallback to `rails console`.
+
+## Possible Issues
+
+* Theoretically, if hirb and wirble(and their dependent gems) conflict with gems in `Gemfile`, it may cause problems. However, I never encounter this situation. Hacking Bundler.setup might be a better way. 
+
+Fell free to report issues in Github's issue tracker. 
+
+## License
+
+See MIT-LICENSE file for details. 
+

data/lib/richrc/version.rb

@@ -1,3 +1,3 @@
 module Richrc
-  VERSION = "0.0.1"
+  VERSION = "0.0.2"
 end

data/richrc.gemspec

@@ -9,7 +9,7 @@ Gem::Specification.new do |s|
   s.authors     = ["miaout17"]
   s.email       = ["miaout17 at gmail.com"]
   s.homepage    = ""
-  s.summary     = %q{Load Wirble and Hirb in Rails 3 without editing Gemfile}
+  s.summary     = %q{Rich Rails Console}
   s.description = %q{Load Wirble and Hirb in Rails 3 without editing Gemfile}
 
   s.rubyforge_project = "richrc"

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification 
 name: richrc
 version: !ruby/object:Gem::Version 
-  hash: 29
-  prerelease: false
+  hash: 27
+  prerelease: 
   segments: 
   - 0
   - 0
-  - 1
-  version: 0.0.1
+  - 2
+  version: 0.0.2
 platform: ruby
 authors: 
 - miaout17
@@ -31,6 +31,8 @@ extra_rdoc_files: []
 files: 
 - .gitignore
 - Gemfile
+- MIT-LICENSE
+- README.md
 - Rakefile
 - bin/richrc
 - lib/richrc.rb
@@ -68,9 +70,9 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 
 rubyforge_project: richrc
-rubygems_version: 1.3.7
+rubygems_version: 1.4.1
 signing_key: 
 specification_version: 3
-summary: Load Wirble and Hirb in Rails 3 without editing Gemfile
+summary: Rich Rails Console
 test_files: []