Update documentation

This commit is contained in:
Roman Efimov
2013-07-16 11:19:30 -05:00
parent fc7e56ccdd
commit 13d65fda10
3 changed files with 3 additions and 3 deletions

View File

@@ -270,7 +270,7 @@
<p><code>RETableViewManager</code> allows to manage the content of any <code>UITableView</code> with ease, both forms and lists. <code>RETableViewManager</code> is built on top of reusable cells technique and provides
APIs for mapping any object class to any custom cell subclass.</p>
<p>The general idea is to allow developers use their own <code>UITableView</code> and <code>UITableViewController</code> instances, providing a layer that synchronizes data with cell appereance.
<p>The general idea is to allow developers to use their own <code>UITableView</code> and <code>UITableViewController</code> instances, providing a layer that synchronizes data with cell appereance.
It almost fully implements <code>UITableViewDelegate</code> and <code>UITableViewDataSource</code> protocols so you don&rsquo;t have to.</p>
</div>

View File

@@ -5,7 +5,7 @@ __Powerful data driven content manager for UITableView.__
`RETableViewManager` allows to manage the content of any `UITableView` with ease, both forms and lists. `RETableViewManager` is built on top of reusable cells technique and provides APIs for mapping any object class to any custom cell subclass.
The general idea is to allow developers to use their own `UITableView` and `UITableViewController` instances, providing a layer that synchronizes data with cell appereance.
It almost fully implements `UITableViewDelegate` and `UITableViewDataSource` protocols so you don't have to.
It fully implements `UITableViewDelegate` and `UITableViewDataSource` protocols so you don't have to.
### _It is still in the early stages of development and it's highly not recommended to use it in production apps._

View File

@@ -54,7 +54,7 @@ NSUInteger REDeviceSystemMajorVersion();
APIs for mapping any object class to any custom cell subclass.
The general idea is to allow developers to use their own `UITableView` and `UITableViewController` instances, providing a layer that synchronizes data with cell appereance.
It almost fully implements `UITableViewDelegate` and `UITableViewDataSource` protocols so you don't have to.
It fully implements `UITableViewDelegate` and `UITableViewDataSource` protocols so you don't have to.
*/
@interface RETableViewManager : NSObject <UITableViewDelegate, UITableViewDataSource>