Consistent naming in viewhelpers

[lsolesen]

It seems that the viewhelpers could be named a bit more consistently.

• function html_link($url, $title = null, $options = array()) {}
• function html_form_tag($method = 'post', $action = null, $options = array()) {} --> why not just form_start()
• function html_form_tag_end() {} --> see krudt_html_form_footer(). Maybe just form_footer()
• function html_text_field($name, $value = null, $options = array()) {} --> see form_text_field()
• function html_password_field($name, $options = array()) {} --> form_password_field() instead
• function html_hidden_field($name, $value = null, $options = array()) {} --> form_hidden_field() instead
• function html_text_area($name, $value = null, $options = array()) {} --> see form_text_field()
• function html_radio($name, $value = null, $checked = false, $options = array()) {} - --> form_radio() instead
• function html_checkbox($name, $checked = false, $options = array()) {} --> form_checkbox() instead
• function html_select($name, $values = array(), $value = null, $options = array()) {} --> form_select()
• function html_options($values = array(), $value = null) {} --> why not form_select_options()
• function krudt_form_footer($submit_title = 'OK', $href_back = null) {} --> why have both this and html_form_tag_end() and not just put the end form tag in the form footer and call it form_end()
• function form_errors($entity) {}
• function form_errors_for($entity, $field) {}
• function form_text_field($entry, $field, $label = null) {} --> why have both this and html_text_field()
• function form_text_area($entry, $field, $label = null) {} --> why have both this and html_text_area()
• function collection_paginate($collection, $size = 10) {} --> should add sticky value

[troelskn]

The form_ prefix is for dealing with domain objects, whereas the html_ prefixed functions just generate html tags. So there is at least some logic to it.

[lsolesen]

How is form_text_field and form_text_area domain objects?