Datasource methods are used to generate tableView cells,header and footer before they are displaying.. Delegate methods provide information about these cells, header and footer along with other user action handlers like cell selection and edit..

The delegate of an UITableView object must adopt the UITableViewDelegate protocol. Optional methods of the protocol allow the delegate to manage selections, configure section headings and footers, help to delete and reorder cells, and perform other actions.

Overview

• Reporting the number of sections and rows in the table.
• Providing cells for each row of the table.
• Providing titles for section headers and footers.
• Configuring the table’s index, if any.
• Responding to user- or table-initiated updates that require changes to the underlying data.

Methods for managing selections, configuring section headers and footers, deleting and reordering cells, and performing other actions in a table view.

The UITableView class is a subclass of UIScrollView, which in turn inherits from UIView, UIResponder, and ultimately NSObject, as shown in Figure 2-2.

UITableViewDataSource is a protocol you implement to provide data for your UITableView . So, with UITableViewDelagate protocol you will be able to response to events like: selection on your rows, editing and several others. With UITableViewDataSource protocol you will be able to feed data into your table.

The UITableViewDelegate protocol declares a method that the delegate must implement to return a cell object that the table view uses when drawing a particular row. (“Table View Cells” gives more detail about this delegate task.) It also allows the delegate to modify visible aspects of the table view.

The basic steps to use delegation are the same for both Objective-C and Swift: Create a delegate protocol that defines the messages sent to the delegate. Create a delegate property in the delegating class to keep track of the delegate. Adopt and implement the delegate protocol in the delegate class.

It’s already well known that UITableView class has become obsolete, and even Apple admits it. It’s poorly customizable and has a variety of issues related to auto-resizing cells, autolayout, etc.

Overview. Table views in iOS display rows of vertically scrolling content in a single column. Each row in the table contains one piece of your app’s content. For example, the Contacts app displays the name of each contact in a separate row, and the main page of the Settings app displays the available groups of settings …

This is the responsibility of the Cell implementation being used. For TableView, it is highly recommended that editing be per-TableColumn , rather than per row, as more often than not you want users to edit each column value differently, and this approach allows for editors specific to each column.

The TableView control is designed to visualize an unlimited number of rows of data, broken out into columns. A TableView is therefore very similar to the ListView control, with the addition of support for columns. For an example on how to create a TableView, refer to the ‘Creating a TableView’ control section below.

With the items set as such, TableView will automatically update whenever the teamMembers list changes. If the items list is available before the TableView is instantiated, it is possible to pass it directly into the constructor. At this point we now have a TableView hooked up to observe the teamMembers observableList.

Creating a TableView is a multi-step process, and also depends on the underlying data model needing to be represented. For this example we’ll use an ObservableList, as it is the simplest way of showing data in a TableView. The Person class will consist of a first name and last name properties.