README.textile in flexible_admin-0.0.3 vs README.textile in flexible_admin-0.0.4

@@ -4,10 +4,23 @@
 
 Flexible Admin is a Rails 3.1 Admin tool to generate an attractive data admin to handle login, data CRUD, search and sort while leaving an easy way to customize the particular needs of an app's custom admin functions.
 
 I have found myself loving other admins for Rails, but many projects need enough admin customization that the value of a engines/magic was offset by the difficulty of customizing.
 
+h4. Depends On
+
+# Rails 3.1+
+
+h4. Kinda needs
+
+# SQL database
+
+h4. Customized for
+
+# Paperclip file attachments
+# SASS stylesheets
+
 h4. Distinctions from other Rails admin gems
 
 Flexible admin generates controller and view files for every model that you are managing, then invites you to get your hands dirty for the customizations of the admin.
 
 It keeps the amount of generated code down by leveraging these gems/libraries to do the heavy lifting
@@ -15,10 +28,15 @@
 # Devise for login
 # Bootstrap for style
 # inherited_resources for rest controllers
 # Database Tables (js) for table searching and sorting
 
+h4. Shortcomings from other Rails admins gems
+
+# Does not natively handle huge amounts of records for viewing.  You would need to implement handling a large number of records for searching/sorting yourself.  (Because Flexible Admin renders every record of a certain model, and then Datatables js presents just 50 at a time that is paginated/filterable/sortable with javascript)
+# Because this is a generator, not an engine, the resource generator might become less effective (=breaks more) as you admin gets more and more customized.  This is because its replacing/inserting code that may have modified.
+
 h2. Getting Started
 
 In your Gemfile
 
 <code>gem 'flexible_admin'</code>
@@ -49,9 +67,13 @@
 h2. Testing
 
 h3. Gem tests
 
 Flexible Admin as a gem is tested with rspec.  The specs cover that the generator generates the right files.  It does not test that you can actually admin in anything after the generator runs.
+
+h3. Tests needed
+
+If possible, my dream tests would run the admin generator on a dummy_app, then step into the dummy app and run a new test suite on how that app behaves after the generator has been run.  If anyone knows how to do that get in touch through github, email or the Issues section.
 
 h4. Working with the tests gotchas
 
 The generator specs really on a dummy Rails app in the spec/dummy folder.  That dummy app has some models, a schema, and a db/test.sqlite3 that matter for the tests.  You might have to dig into those if you are having problems modding the specs.  One of the generators reads the models and the database columns to generate the admin forms, and so the dummy app has those files to test off it.
 
\ No newline at end of file