maintain 0.1.0 → 0.1.1

data/.gitignore

@@ -1 +1,2 @@
-coverage/
+coverage/
+*.gem

data/README.markdown

@@ -61,36 +61,41 @@ You could also do:
 
 	Foo.new.state > old	#=> true
 
-Bitmasking
+Hooks
 -
 
-Sometimes you need to store a simple combination of values. Sure, you could add individual columns for each value to your
-relational database - or you could implement a single bitmask column:
+**Maintain** can hook into state entry and exit, and provides a number of mechanisms for doing so:
+
+	class Foo < ActiveRecord::Base
+	  maintains :state do
+	    state :active, :enter => :activated
+	    state :inactive, :exit => lambda { self.bar.baz! }
+	  end
+	
+	  def activated
+	    puts "I'm alive!"
+	  end
+	end
+
+Of course, maybe that's not your style. Why not try this?
 
 	class Foo
 	  extend Maintain
-	  maintains :state, :bitmask => true do
-	    # NOTE: Maintain will try to infer a bitmask value if you do not provid  an integer here,
-	    # but if you don't -- and you re-order your state calls later -- all stored bitmasks will
-	    # be invalidated. You have been warned.
-	    state :new, 1
-	    state :old, 2
-	    state :borrowed, 3
-	    state :blue, 4
+	  maintains :state do
+	    state :active
+	    state :inactive
+
+	    on :enter, :active, :activated
+	    on :exit, :inactive do
+	      bar.baz!
+	    end
+	  end
+
+	  def activated
+	    puts "I'm alive!"
 	  end
 	end
-	
-	foo = Foo.new
-	foo.state 						#=> nil
-	foo.state = [:new, :borrowed]
-	foo.state 						#=> [:new, :borrowed]
-	foo.new? 						#=> true
-	foo.borrowed? 					#=> true
-	foo.blue? 						#=> false
-	foo.blue!
-	foo.blue? 						#=> true
-	
-	# foo.state will boil happily down to an integer when you store it.
+
 
 Aggregates
 -
@@ -114,55 +119,49 @@ But why not just add the following?
 	foo.status = :borrowed
 	foo.starts_with_b?		#=> true
 
-Named Scopes
+Bitmasking
 -
 
-**Maintain** knows all about ActiveRecord. Adding states and aggregates will automatically create named scopes on ActiveRecord::Base
-subclasses for those states! Check it:
+Sometimes you need to store a simple combination of values. Sure, you could add individual columns for each value to your
+relational database - or you could implement a single bitmask column:
 
-	class Foo < ActiveRecord::Base
+	class Foo
 	  extend Maintain
-	  maintains :state do
-	    state :active
-	    state :inactive
+	  maintains :state, :bitmask => true do
+	    # NOTE: Maintain will try to infer a bitmask value if you do not provide an integer here,
+	    # but if you don't -- and you re-order your state calls later -- all stored bitmasks will
+	    # be invalidated. You have been warned.
+	    state :new, 1
+	    state :old, 2
+	    state :borrowed, 3
+	    state :blue, 4
 	  end
 	end
 	
-	Foo.active		#=> []
-	Foo.inactive	#=> []
+	foo = Foo.new
+	foo.state 						#=> nil
+	foo.state = [:new, :borrowed]
+	foo.state 						#=> [:new, :borrowed]
+	foo.new? 						#=> true
+	foo.borrowed? 					#=> true
+	foo.blue? 						#=> false
+	foo.blue!
+	foo.blue? 						#=> true
+	
+	# foo.state will boil happily down to an integer when you store it.
 
-Hooks
+Named Scopes
 -
 
-**Maintain** can hook into state entry and exit, and provides a number of mechanisms for doing so:
+**Maintain** knows all about ActiveRecord - it even extends ActiveRecord::Base by default. So it stands to reason that adding states
+and aggregates will automatically create named scopes on ActiveRecord::Base subclasses for those states! Check it:
 
 	class Foo < ActiveRecord::Base
-	  maintains :state do
-	    state :active, :enter => :activated
-	    state :inactive, :exit => lambda { self.bar.baz! }
-	  end
-	
-	  def activated
-	    puts "I'm alive!"
-	  end
-	end
-
-Of course, maybe that's not your style. Why not try this?
-
-	class Foo
-	  extend Maintain
 	  maintains :state do
 	    state :active
 	    state :inactive
-
-	    enter :active, :activated
-	    exit :inactive do
-	      bar.baz!
-	    end
-	  end
-
-	  def activated
-	    puts "I'm alive!"
 	  end
 	end
-
+	
+	Foo.active		#=> []
+	Foo.inactive	#=> []

data/VERSION

@@ -1 +1 @@
-0.1.0
+0.1.1

data/lib/maintain.rb

@@ -1,10 +1,10 @@
 module Maintain
   # We're not really interested in loading anything into memory if we don't need to,
   # so Maintainer, Value, and the Value subclasses are ignored until they're needed.
-  autoload(:Maintainer, 'lib/maintain/maintainer')
-  autoload(:Value, 'lib/maintain/value')
-  autoload(:BitmaskValue, 'lib/maintain/bitmask_value')
-  autoload(:IntegerValue, 'lib/maintain/integer_value')
+  autoload(:Maintainer, 'maintain/maintainer')
+  autoload(:Value, 'maintain/value')
+  autoload(:BitmaskValue, 'maintain/bitmask_value')
+  autoload(:IntegerValue, 'maintain/integer_value')
 
   # The core class method of Maintain. Basic usage is:
   # 

data/maintain.gemspec

@@ -0,0 +1,74 @@
+# Generated by jeweler
+# DO NOT EDIT THIS FILE DIRECTLY
+# Instead, edit Jeweler::Tasks in Rakefile, and run the gemspec command
+# -*- encoding: utf-8 -*-
+
+Gem::Specification.new do |s|
+  s.name = %q{maintain}
+  s.version = "0.1.1"
+
+  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
+  s.authors = ["Flip Sasser"]
+  s.date = %q{2010-02-19}
+  s.description = %q{
+      Maintain is a simple state machine mixin for Ruby objects. It supports comparisons, bitmasks,
+      and hooks that really work. It can be used for multiple attributes and will always do its best to
+      stay out of your way and let your code drive the machine, and not vice versa.
+    }
+  s.email = %q{flip@x451.com}
+  s.extra_rdoc_files = [
+    "README.markdown"
+  ]
+  s.files = [
+    ".gitignore",
+     "README.markdown",
+     "Rakefile",
+     "VERSION",
+     "lib/maintain.rb",
+     "lib/maintain/bitmask_value.rb",
+     "lib/maintain/integer_value.rb",
+     "lib/maintain/maintainer.rb",
+     "lib/maintain/value.rb",
+     "maintain.gemspec",
+     "spec/active_record_spec.rb",
+     "spec/aggregates_spec.rb",
+     "spec/bitwise_spec.rb",
+     "spec/comparing_state_spec.rb",
+     "spec/defining_states_spec.rb",
+     "spec/hooks_spec.rb",
+     "spec/integer_spec.rb",
+     "spec/maintain_spec.rb",
+     "spec/object_spec.rb",
+     "spec/proxy_spec.rb",
+     "spec/setting_state_spec.rb"
+  ]
+  s.homepage = %q{http://github.com/flipsasser/maintain}
+  s.rdoc_options = ["--charset=UTF-8"]
+  s.require_paths = ["lib"]
+  s.rubygems_version = %q{1.3.5}
+  s.summary = %q{A Ruby state machine that lets your code do the driving}
+  s.test_files = [
+    "spec/active_record_spec.rb",
+     "spec/aggregates_spec.rb",
+     "spec/bitwise_spec.rb",
+     "spec/comparing_state_spec.rb",
+     "spec/defining_states_spec.rb",
+     "spec/hooks_spec.rb",
+     "spec/integer_spec.rb",
+     "spec/maintain_spec.rb",
+     "spec/object_spec.rb",
+     "spec/proxy_spec.rb",
+     "spec/setting_state_spec.rb"
+  ]
+
+  if s.respond_to? :specification_version then
+    current_version = Gem::Specification::CURRENT_SPECIFICATION_VERSION
+    s.specification_version = 3
+
+    if Gem::Version.new(Gem::RubyGemsVersion) >= Gem::Version.new('1.2.0') then
+    else
+    end
+  else
+  end
+end
+

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: maintain
 version: !ruby/object:Gem::Version 
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors: 
 - Flip Sasser
@@ -31,6 +31,7 @@ files:
 - lib/maintain/integer_value.rb
 - lib/maintain/maintainer.rb
 - lib/maintain/value.rb
+- maintain.gemspec
 - spec/active_record_spec.rb
 - spec/aggregates_spec.rb
 - spec/bitwise_spec.rb