Comments on: Combining multiple UITextFields and a UITableView in a nice way for an iPhone app: part 2

By: Dirk de Kok

Dirk de Kok — Thu, 07 Apr 2011 14:37:23 +0000

Hi @arri,

well the question is when to use a datasource? When filling in any value, or when the save button is touched. Right now I choose to have a separate way of storing temporary values, namely in the preserved cells and only update the datasource when the save button is hit.

Yes this is not good for performance, but hey who’s gonna build a form on an iPhone with 50, 100 or 200 fields? So I think that problem is limited

@ali, @arri means that on the change of a UITextField, UIButton etc. you store this value immediately in a temp array or evey as you are trying, into variables declared in the controller. Just think about when you really use/persist these values.

By: Ali

Ali — Tue, 05 Apr 2011 20:55:26 +0000

your approach looks better. But, can you give a sample code or an example of doing this.

Also, I did not understand your words(ou are storing data in the tableview itsself, while this should be done
in your data-model, managed through the contoller object.)??

Now I am storing the data in variables declared in the controller, is this wrong?

By: arri

arri — Sun, 03 Apr 2011 22:45:27 +0000

this approach will lead to performance issues when your tables gets larger.
the purpose of the cell identifier is make it easy/possible to re-use cells,
what you’re doing is the opposite.

your problem is not the fact cells get re-used, but you’re missing the
point on the concept ‘DataSource’.
You are storing data in the tableview itsself, while this should be done
in your data-model, managed through the contoller object.

one way is to keep an array that references the data for entry.

By: Ali

Ali — Fri, 01 Apr 2011 18:30:37 +0000

The simplest way I found from one website is to put an NSString variable for every textfield and update its value from the textfield text in the (- (void)textFieldDidEndEditing:(UITextField *)textField) that the textfield delegate will call. Then in every textfield creation code in (cellForRowAtIndexPath) you will put the text of this textfield to be the value of its NSString variable.

By: Implementing a Data Entry UI on iPhone with Action Button « GQAdonis

Implementing a Data Entry UI on iPhone with Action Button « GQAdonis — Tue, 15 Feb 2011 20:29:27 +0000

[...] Implementing a Form Inside a UITableView–This uses a method for ensuring that data can be edited, but I am not so fond of the method that prevents the reuse of cells in this implementation. As alternatives, the Apple TaggedLocations Sample provides some good clues. Also, this post, from Twitterific's creators has some excellent guidance on this as well. Finally, IBAForms is an open source project that abstracts the entire process in a nice way that includes full source code. [...]