The adoption of AGgrid is truly a revolution in the management of tabular data! 100% of our forms use grids that must be high-performance, and this is truly a fantastic upgrade for our development!
But I hope that the most used, simple and taken for granted use will not be forgotten (as often happens): the Adapter for the Twebdatasource and therefore TwebClientDataset, as is natural that it is present. Will it be there?
If it will be possible to manage filters in the headers of each column (filter edits, not popup, as I have already seen in the demos on the AgGrid site), assign CSS and above all allow powerful editing directly in the grid, I think this is a truly useful innovation.
In the demos it seems very high-performance, there are excellent prospects. I am eager to test its features thoroughly
So far we encountered very difficult challenges to make AgGie working with the dataset concept. Although it is indeed very desirable to have this functionality, we cannot guarantee it at this moment we will be able to overcome these difficulties
I understand the difficulty.
But if you really want TMS Web Core to become a powerful tool on par with Delphi for VCL, you have to deal with the most used component and therefore the most powerful possible: the grid connected to the dataset management, a cornerstone of the Delphi philosophy.
Even if someone will tell me that on the web things are different (json, etc..) it is stupid to think that a powerful grid that is "Datadriven" with datasets is not an incredible advantage for those who have to migrate large applications from VCL, maintaining the same logic.
The current TWebDbgrid is really poor (totals, filters, searches in headers) and above all really too slow as an architecture to be used in "serious" web applications, so it should be discarded.
While the FNCDatagrid promises well, but it is certain that the "web" version is actually the Cinderella in the development priorities.
The introduction of Ag-Grid introduces hope, since it has advanced features (is it also possible to interact with the "professional" version?) but we know everything without the integration of datasets, and being forced to use Json, Strings and other alternatives is like having a formula 1 car that runs with the handbrake on.
I say this in the interest not only of my development, which must be as "comfortable" and fast as possible, but in the interest of a great product that is TMS Web Core in which I have faith.
If we didn’t understand this, we would not already have spent almost a year R&D on this. But it is not simple because AgGrid was not designed with having a TDataSet concept in mind, so we need to really think out of the box to bridge it to it.