README.textile in grimen-dry_scaffold-0.2.2 vs README.textile in grimen-dry_scaffold-0.2.3

@@ -2,11 +2,11 @@
 
 A Rails scaffold generator that generates DRYer, cleaner, and more useful code.
 
 h2. Description
 
-DryScaffold is a replacement for the Rails scaffold generator that generates code that most people end up deleting or rewriting anyway because of the unusable code. The scaffold concept is powerful, but it has more potential than generating messy and almost useless code. The goal with DryScaffold is to generate DRY, beautiful, and standards compliant code based on common patterns without adding a lot of magic.
+DryScaffold is a replacement for the Rails scaffold generator that generates code that most people end up deleting or rewriting anyway because of the unusable code. The scaffold concept is powerful, but it has more potential than generating messy and almost useless code - something that might change with Rails 3 though. The goal with DryScaffold is to generate DRY, beautiful, and standards compliant code based on common patterns without adding a lot of assumptions.
 
 h3. Key Concepts:
 
 * Controllers that are DRY, RESTful, no code-smells, following conventions, and implementing VERY common patterns.
 * Views that are DRY, semantic, standards compliant, valid, and more useful in development.
@@ -157,13 +157,12 @@
 
 h3. More To Come... (TODO)
 
 These are things I have in mind:
 
-* Generation of Rails builder stubs automatically for formats atom/rss.
-* Make routing smarter; if route is already declared in _config/routes.rb_, then don't generate it (no duplication).
-* Break up into multiple generators as dependencies (like Rails generators): dry_controller, dry_views, dry_scaffold, ...
+* Handle belongs_to, i.e. specify MODEL --belongs-to PARENT_MODEL, which generates proper routes, proper before-filters if inherited_resources-controller, adding belongs_to-association in model, and correct form_for arguments.
+* Choose test suits: testunit/shoulda/rspec
 
 h2. Setup
 
 Installing DryScaffold is easy as 1-2-3...nah, really:
 
@@ -250,12 +249,10 @@
 
 <pre>_actions:new,create,quack,index,...</pre>
 
 You can override what actions that should be generated directly - including custom actions.
 
-NOTE: Sorry for the a bit ugly prefix (_), but I had to trick the Rails generator a bit to get this working for now. This is definitely something I want to fix sooner or later, but I skipped that for now with this small hack.
-
 h4. Default Actions (REST)
 
 If no actions are specified, the following REST-actions will be generated by default:
 
 * @show@
@@ -285,12 +282,10 @@
 
 <pre>_formats:html,xml,txt,...   # <=> _respond_to:html,xml,txt,...</pre>
 
 You can override what respond_to-formats that should be generated directly - only for REST-actions right now because I tried to avoid bad assumptions.
 
-NOTE: Sorry for the a bit ugly prefix (_), but I had to trick the Rails generator a bit to get this working for now. This is definitely something I want to fix sooner or later, but I skipped that for now with this small hack.
-
 h4. Default Formats
 
 If no formats are specified, the following formats will be generated by default:
 
 * @html@  => Template: resource.html.haml
@@ -416,6 +411,6 @@
 
 If you experience any issues/bugs or have feature requests, just file a GitHub-issue or send me a message.
 If you think parts of my implementation could be implemented nicer somehow, please let me know...or just fork it and fix it yourself! =)
 At last, positive feedback is always appreciated!
 
-Copyright (c) 2009 Jonas Grimfelt
+Copyright (c) 2009 Jonas Grimfelt, released under MIT-license
\ No newline at end of file