jarwol / atable Goto Github PK

By default, every column is resizable and movable, and the table is sortable by all columns. Allow the user to configure each of these properties at the table level, and resizable/sortable at the column level.

Rather than add a fixed number of pixels to the width of each column to account for a possible sort arrow being added, simply adjust the width as needed.

Assign the resize indicator div an id in the form of "resizeX", where X is some unique integer. In order to guarantee a unique id, get a list of all .grayout elements in the document, and choose the largest id so far. Then take the integer from the end of the id, and increment it.

Adding the dataset to the backbone collection takes a substantial amount of time when number of rows reaches the hundreds of thousands. Look into changing the rows collection from a backbone collection into a custom object.

Implement a workaround for the lack of Blob support, and then tackle any other issues that arise during testing in IE.

Instead of requiring a 2-dimensional array of data, allow receivedData to return an array of JSON objects {columnName : value}.

When rows are removed from the table upon re-rendering or scrolling the table, the DOM objects are not garbage collected. This causes a massive memory leak.

The dashed border is very inconsistent when dragging one column header over another.

Rows are not correctly added/removed from the DOM as the table is scrolled up and down.

If the vertical scrollbar is visible, subtract the scrollbar's width from the last column of each row. Otherwise there will be horizontal overflow in the tbody.

Browser compatibility is poor for setDragImage (to wipe out the ghost image during a resize operation). Use mousemove/mouseup events for resizing columns to avoid these issues.

Using Foundation adds some styles to the ATable that cause its appearance to be off.

Provide a filter(colName, str) method, causing the table to display only rows which contain the text str in the specified column.

Figure out how to not display the standard drop effect icons, and instead set the cursor to e-resize for resizing or pointer/move for moving.

Ensure that the sort arrow renders on the same line as the column label in Firefox.

Allow users to pass in a formatter function that will take the value of a cell and return the formatted value for all cells in a column.

Multiple atables on a page can result in columns being moved to other atables. This should be prevented by stamping a table identifier on the column during the dragStart event, and checking it against the target table before attempting a move operation.

Set the idAttribute of the ColumnCollection to Column.name to allow constant time access to columns by their name. Remove the unnecessary columnsByName hash.

When columns are hidden, the column header's cellIndex property may not match up with its index in atable.columns. Store a column's name in the DOM element so that it can be used to retrieve the correct column regardless of its position in the DOM.

Use gruntjs to automate build tasks such as testing, validating with jshint, and concatenating/minifying the code.

Allow the user to drag a column header to any cell in the destination column, instead of only the column header. Implement a better visual cue when the move operation is started.

Allow the user to configure a minimum and maximum width for resizable columns.

Allow the user to provide fetchData functions that return data an arbitrary number of times (possible indefinitely). The table should either completely refresh or append the new rows, based on a boolean parameters.

Update unit tests to use a callback function instead of web workers so that they can run on older browsers.

If an atable is rendered in a container with display: none set, the right border disappears. Other display bugs may be occurring as well.

Allow users to resize, reorder, add, remove, and rename columns and sort the table programmatically.

The column headers and cells get out of sync if the table's parent element is a container with an explicit width set, and the table is resized to be larger than that width.

Allow the user to provide an array of CSS classes to apply to cell content. They should be configurable at the table and column level.

Allow the user to pass in a function responsible for delivering data to the ATable. Rather than the web worker function which calls self.postMessage(data), the data function will call ATable.receivedData(data) directly.

Underscore 1.5 no longer allows bindAll to be called without function names to bind to all scoped functions. Call it with each function that requires a reference to the table.

Sort by the displayed text content, disregarding HTML tags.

Set cell content to be contenteditable if the user specifies an editable property in the column config or the table config.

Allow the user to prevent columns from rendering in the DOM by setting visible : false. Also add public API methods ATable.hideColumn(name|index) and ATable.showColumn(name).

If a column is moved, the incorrect value may be passed to the formatter function when cells are rendered/replaced. This happens because the column order should not be taken into account when indexing the dataset by the sortColumn.

When dragging the scrollbar up or down, the cursor gets slightly ahead. This may mean the buffer rows are shrinking faster than the scrollTop is moving.

Only display the dashed border indicating a valid drop target if a column is dragged onto another column within its own ATable.

After a column resize, tbody cells are out of sync with thead cells.

Implement exportJson() and exportArray() which will return the data in the table as an array of objects or an array of arrays.

Allow the user to pass in callbacks to be executed upon events:

• Add/remove column
• Move column
• Resize column
• Sort

There's a bug that causes a slow down of the table and incorrect rendering when scrolling back up after scrolling down.