At 11:51 AM -0700 5/26/99, Creative Digital Publishing Inc. wrote:
>>2.    Table object with 11 rows of text
>>This sounds attractive because I can put some other additional
>>info on each line apart from the text to be selected.
>
>With a custom drawing routine, you can do the same with a list.

Right.  The only reason to use a table instead of a list is because you
need to put controls in the rows.

For example, the address book "list" view is really a list, because it's
essentially read only.  And the to do and datebook app "list" views are
tables, because you need to have check boxes, popups, and editable fields
on each line.

11 fields sounds like a mess to manage, and probably only wastes memory.
If you don't need to edit the data in this view, use a list.

                                --Bob


Reply via email to