Comments for D17's blog http://blog.d-17.com About hardcore technology and softcore business Wed, 18 Jan 2012 11:55:30 +0000 hourly 1 http://wordpress.org/?v=3.0.3 Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app by doc viewer http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-16787 doc viewer Wed, 18 Jan 2012 11:55:30 +0000 http://blog.d-17.com/?p=85#comment-16787 <strong>doc viewer...</strong> [...]Combining multiple UITextFields and a UITableView in a nice way for an iPhone app « D17′s blog[...]... doc viewer…

[...]Combining multiple UITextFields and a UITableView in a nice way for an iPhone app « D17′s blog[...]…

]]> Comment on Iphone 3Gs announcement review – ups and downs by IPOD WANTED http://blog.d-17.com/2009/06/iphone-3gs-review/comment-page-1/#comment-16175 IPOD WANTED Fri, 30 Dec 2011 11:52:14 +0000 http://blog.d-17.com/?p=71#comment-16175 <strong>IPOD WANTED...</strong> [...]Iphone 3Gs announcement review – ups and downs « D17′s blog[...]... IPOD WANTED…

[...]Iphone 3Gs announcement review – ups and downs « D17′s blog[...]…

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app: part 2 by Dirk de Kok http://blog.d-17.com/2009/10/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app-part-2/comment-page-1/#comment-11057 Dirk de Kok Thu, 07 Apr 2011 14:37:23 +0000 http://blog.d-17.com/?p=118#comment-11057 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. 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.

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app: part 2 by Ali http://blog.d-17.com/2009/10/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app-part-2/comment-page-1/#comment-11013 Ali Tue, 05 Apr 2011 20:55:26 +0000 http://blog.d-17.com/?p=118#comment-11013 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? 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?

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app: part 2 by arri http://blog.d-17.com/2009/10/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app-part-2/comment-page-1/#comment-10974 arri Sun, 03 Apr 2011 22:45:27 +0000 http://blog.d-17.com/?p=118#comment-10974 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. 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.

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app: part 2 by Ali http://blog.d-17.com/2009/10/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app-part-2/comment-page-1/#comment-10920 Ali Fri, 01 Apr 2011 18:30:37 +0000 http://blog.d-17.com/?p=118#comment-10920 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. 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.

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app: part 2 by Implementing a Data Entry UI on iPhone with Action Button « GQAdonis http://blog.d-17.com/2009/10/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app-part-2/comment-page-1/#comment-9653 Implementing a Data Entry UI on iPhone with Action Button « GQAdonis Tue, 15 Feb 2011 20:29:27 +0000 http://blog.d-17.com/?p=118#comment-9653 [...] 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. [...] [...] 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. [...]

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app by Dirk de Kok http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-6494 Dirk de Kok Wed, 13 Oct 2010 09:51:42 +0000 http://blog.d-17.com/?p=85#comment-6494 @chris, yes <a href="http://blog.d-17.com/2009/10/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app-part-2/" rel="nofollow">see part 2</a> for a way of doing this, the UITableView reuse of cells is very good when you want to scroll through 100s of rows, not for making form-like views @daniele looks good, I'l give it a go @chris, yes see part 2 for a way of doing this, the UITableView reuse of cells is very good when you want to scroll through 100s of rows, not for making form-like views

@daniele looks good, I’l give it a go

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app by Daniele Demichelis http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-6480 Daniele Demichelis Tue, 12 Oct 2010 10:12:03 +0000 http://blog.d-17.com/?p=85#comment-6480 Hi, I just released on github a framework to create and manage form in iPhone. The URL is http://github.com/danidemi/FormFramework . It allows the programmer to create a nice form in a way that resemble HTML forms. As explained in your article, the framework draws form with UITableView, indeed. Hi, I just released on github a framework to create and manage form in iPhone. The URL is http://github.com/danidemi/FormFramework . It allows the programmer to create a nice form in a way that resemble HTML forms. As explained in your article, the framework draws form with UITableView, indeed.

]]> Comment on Combining multiple UITextFields and a UITableView in a nice way for an iPhone app by Chris http://blog.d-17.com/2009/08/combining-multiple-uitextfields-and-a-uitableview-in-a-nice-way-for-an-iphone-app/comment-page-1/#comment-6477 Chris Tue, 12 Oct 2010 01:46:10 +0000 http://blog.d-17.com/?p=85#comment-6477 All you need to do is retain the cells you've added, so they don't get released when they scroll out of view. You should read the documentation for UITableView- it's all in there. Look at the cell reuse mechanism as well, which is designed to reduce memory consumption with large tables. All you need to do is retain the cells you’ve added, so they don’t get released when they scroll out of view. You should read the documentation for UITableView- it’s all in there. Look at the cell reuse mechanism as well, which is designed to reduce memory consumption with large tables.

]]>