Hello
I’m currently testing jqWidgets for implementation in a rather large Angular app. While I really like the grid functionality, it seems there are potential deal breakers. But before I write off the grid, I wanted to see if this is a basic misunderstanding on my part.
The jqWidget grids seem to break the paradigm of data binding. In fact, if I bind myData to a data adapter, there is no reference to myData through the grid. Additionally, making changes to myData or dataAdapter.records seems to have no impact on the display of the records themselves, and therefore there is no true binding. It seems all manipulation of records in the grid must be done through the grid API, and cannot be done directly to the data which is the initial source for the grid.
The problem here is the potential impact on performance, and the overhead it having to be dependent upon the API to make simple updates to the data. If I MUST manipulate data via the grid API and not via the data directly, there’s also a significant amount of manual synchronization that will need to occur. Part of the purpose of using Angular is to take advantage of data binding for this reason.
For instance, if I want to update a column, I would generally just update the source array members:
myData[i].isSelected = true;
Then data binding would handle the updates to any references, including displayed references. This does not seem possible for the jqWidgets implementation.
Are my assumptions correct?
