roles_generic 0.2.3 → 0.2.4

data/README.markdown

@@ -12,14 +12,10 @@ I have developed the following *roles* gems for popular ORMs that all support th
 
 Feel free to roll your own ORM extension for your favorite ORM!
 
-## Status update (4 sept, 2010)
 
-Roles generic has now been refactored in order to tidy up the code base and make it even more generic, flexible and easy to extend.
+## Status update (12 sept, 2010)
 
-Currently I'm not sure if the generator fully works. It has a dependency on [rails3_artifator](http://github.com/kristianmandrup/rails3_artifator), which should work.
-However my gem to test generators (called [generator-spec](http://github.com/kristianmandrup/generator-spec), is currently not functioning as it has dependencies to other gems that have undergone major
-
-refactorings lately. Let me know if the generator works or if not, see if you can make it work using *rails3_artifactor* and let me know the fix ;) 
+Roles generic has now been refactored in order to tidy up the code base and make it even more generic, flexible and easy to extend. It should now work! Please let me know if you have any issues ;)
 
 ## Install
 
@@ -29,17 +25,20 @@ refactorings lately. Let me know if the generator works or if not, see if you ca
 
 The library comes with the following role models built-in:
 
+Inline roles (in User model):
 * admin_flag (Boolean flag - 'admin' or not)
 * role_string (String)
 * roles_string (Comma separated String - note: no role name must have a comma in its name!)
 * role_strings (Set of Strings)
 * roles_mask (Integer mask)
+
+Using separate Role model:
 * one_role (relation to a Role model instance)
 * many_roles(Set of Role relationships)
 
 Note: The following examples use RSpec to demonstrate usage scenarios.
 
-Examples of configuring for the other strategies can be found in the wiki pages.
+Examples of configuring for the other strategies can be found on the wiki pages.
 
 ## Example : admin_flag
 
@@ -85,6 +84,8 @@ Data Mapper with persistent attributes :name and :admin_flag
   end
 </pre>
 
+_Note:_ I recommend using s specific ORM roles gem such as *roles_data_mapper* instead. But this approach might be a good starting point for developing a *roles* gem for an ORM that is not supported ;)
+
 ## Role API
 
 ### Instance methods

data/VERSION

@@ -1 +1 @@
-0.2.3
+0.2.4

data/roles_generic.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{roles_generic}
-  s.version = "0.2.3"
+  s.version = "0.2.4"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = ["Kristian Mandrup"]
-  s.date = %q{2010-09-11}
+  s.date = %q{2010-09-12}
   s.description = %q{Generic role strategies sharing the same API. Easy to insert in any model}
   s.email = %q{kmandrup@gmail.com}
   s.extra_rdoc_files = [

metadata

@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
   segments: 
   - 0
   - 2
-  - 3
-  version: 0.2.3
+  - 4
+  version: 0.2.4
 platform: ruby
 authors: 
 - Kristian Mandrup
@@ -14,7 +14,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2010-09-11 00:00:00 +02:00
+date: 2010-09-12 00:00:00 +02:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency