I’ve been struggling with this since I saw the 1st news about Vaadin 8 and I have yet to see a satisfactory answer.
I don’t want to write a class for every data I want to display in a listing. My app has tens of reports of “simple” data coming mainly from database queries; most of them even have their database View in order to customize some attributes like column names or derivated columns. Why in do world would I want to have to write a class for each of those?? It goes against the principle of automation, genericism and reusing code.
I have nothing against the new data providing mechanism for grids and tables, but there should be other ways. I think that, at least, directly adding and removing “items” the old way, in memory, should have been kept. It’s a basical feature that any framework does allow, otherwise limiting functionality severely.
This is the main reason that is preventing my organization from updating to v8, and I understand we can’t be forever stuck in an obsolete version.
I’ve seen some recomendations here and there on how to accomplish this, but I find all of them more or less cumbersome to a certain degree, and the extra paraphernalia needed to get them working is really keeping me away from attempting them.
