
Public Member Functions | |
| __construct ($args=NULL) | |
| value2db ($value=FALSE) | |
| db2value ($value=FALSE) | |
| render2form (&$obj) | |
| parseForm (&$obj) | |
| getFormElement (&$obj, $title=NULL) | |
Public Attributes | |
| $type | |
| $download = FDOWNLOAD_ALWAYS | |
| $name = '' | |
| $title = '' | |
| $default | |
| $tooltip = '' | |
| $invalid | |
| $func_renderToForm | |
| $func_parseForm | |
| $func_renderListHead | |
| $func_renderListRow | |
| $func_getFormElement | |
| $view_in_forms | |
| $view_in_lists | |
| $log_changes = true | |
| $export = true | |
| $export_csv = false | |
DbItems are objects representing db-elements. DbItems have fields of different types. Some of these field types directly refer to there counterpart in sql. Some provide additional layers of abstraction. The Field-class tries to find special methods for rendering end convertion. Actually those methods (eg. XXX_renderToForm, where 'XXX' could be 'task') could be members of the derived classes, but refering to existing function allows to overwrite already defined classes by new themes.
Mental note: I doubt that overwriting an existing function is easier than overwriting a class-method.
Definition at line 33 of file db_item.inc.php.
1.5.1-p1