| Feature | Mozilla Firefox | Internet Explorer |
|---|---|---|
| Data handling | ||
|
Database independent Meaning you as developper may load/save the table's data however you wish (via AJAX, via POST-Requests, from files, from websevices, from databases or whatever your datasource is). |
Yes | Yes |
|
Lazy data loading possible Using the Cachtable you may implement a dataProvider only loading the really needed data (i.e. these records actually visible on the screen). This feature is essentially for working with very large datasets. So you can replace the "page 1 of 767" pattern. |
Yes | Yes |
|
Caching possible The CacheTable by default caches all already loaded data. Cachesize is customizable, setting its size to 0 will switch the caching off. |
Yes | Yes |
|
Asynchronous loading possible To avoid that your whole website will be blocked during Database-Queries (or any other data loading algorithm you may use), it's possible to do this async (e.g. using AJAX) |
Yes | Yes |
|
Progressive load By default the table's progressive load mechanism is on. This means that always when "nothing" is to do, the table loads further data in the background. Works only together with async loading! |
Yes | Yes |
| Display features | ||
|
Renderers for each column possible You may use so-called renderers to e.g. format the shown value of a concrete table cell. The renderers may be set per column. This allows you to seperate the "real" data form the screen representation. |
Yes | Yes |
|
Columns are styleable You may define a style for each column (setColumnFormat()). This can be used to get e.g. right-aligned columns. | Yes | Yes |
|
Rows are styleable You my pass styles and HTML-Attributes each row should get. The concrete row-style can be alternating (to increase readability) or data-dependent. | Yes | Yes |
|
Setting column widths You, as developper, may define a width for each column of the table. | Yes | Yes |
|
Resizeable columns The user may resize the column's width in the table-head. | Yes | No |
| Editing the table | ||
|
Editable Using the edit_table, the whole table becomes editable. By default all columns can be changed using a text-input field. Undoing all changes is possible. As developper you can easily access all changed / inserted data (e.g. to store it in your datasource). |
Yes | Yes |
|
Custom editors possible Editors may be set per column, e.g. select-inputs or number-inputs, whatever you like to restrict the possible values the user may enter. | Yes | Yes |
|
Read-only columns possible If not every column should be editable by the user, you may define read-only columns. Set this column's editor to null to get a read-only column. | Yes | Yes |
| Built-in functionality | ||
|
Observeable The coretable uses the in CoreAll built-in observer-pattern to throw events if the user clicks / double-clicks on the table-header or the table-body. You as developer may react on these user actions, e.g. sort the table. | Yes | Yes |
|
Selectable One or more rows are selectable. As developer you can easily access the selected columns. Holding down the Ctrl- or Shift-Key is supported so select multiple rows or a whole section. The selection mode may be set to multiple, single or none. | Yes | Yes |
|
Keyboard support A number of keyboard-shortcuts may be used to navigate and edit the table. | Yes | Partly |
|
Mousewheel support If a CacheTable gets a scrollbar you may also scroll through the whole dataset using the mousewheel. | Yes | No |
|
Printable The table may be printed (it creates a prinder friendly version therfore) totally or partially. Partially means all selected rows. | Yes | Yes |
|
Exportable The table may be exported to the clipboard totally or partially. Partially means all selected rows. | Yes | Yes |