UITextView appropriate for a status window?

[jo5729]

I'm trying to create a status window that would display logging information similar to the following:

27-JUN-11 01:12     Request Sent
27-JUN-11 01:12     Response Received: 200/OK
27-JUN-11 01:14     Request Sent
27-JUN-11 01:14     Request timed out
27-JUN-11 01:14     Request Sent
27-JUN-11 01:14     Response Received: 202/ACCEPTED
.
.
.

is a UITextView appropriate for this? Is there something better?

I have one view with a view controller (and view) that is posting the requests, and a second view controller (and view) that is running the log window. There is a root view controller with a tab bar controller that allows the user to switch between them.

Also, should I write the log messages directly to the UI element, or should I write the responses to a log object, and bind the log object to the UI element? I am not exactly sure how to do the latter method, using objective C, so any help there would be appreciated.

Thanks!

[dljeffery]

I've thought about adding a log view into an iOS app as well (business app) and my planned approach is:

1) write log entries into the (existing) database via Core Data
2) use a UITableView for display of the data

Unless your log is very short, I don't think that using a UITextView would be a good approach. And using a UITableView will be a very easy approach if your logs are either in a database or a transient array. (I don't know if you care about maintaining the log between sessions or not; I do, personally, hence the use of the database.)

In any case, set up a log object; don't try to write directly into the view across controllers.

[MatthewD]

UITextView should work fine. You'll probably want to update the UITextView after resetting the text to scroll to the bottom.

To bind the log object to the UITextView, I recommend looking into Key-Value Observing.

[jo5729]

Originally Posted by dljeffery

I've thought about adding a log view into an iOS app as well (business app) and my planned approach is:

1) write log entries into the (existing) database via Core Data
2) use a UITableView for display of the data

I'm liking this approach, but I know I do not have the iOS experience to design and develop this correctly. I've got a prototype going on the side to learn, but I'd like to get a solution quicker.

I posted an ad on the jobs forum to see if I could hire someone experienced to help me design and implement this (correctly!), and if we can do it generically enough, open source it.

It seems like it could be a compartmentalized problem that a open source solution (similar to the ASIHttp project) could address to make everyone's life a little easier, similar to how log4j works in Java.