3 ms·
An event driven, local-first, UI that automatically reacts to changes in the underlying database is a pretty old idea. https://docs.microsoft.com/en-us/dotnet/
by intrepidhero 5y ago
An event driven, local-first, UI that automatically reacts to changes in the underlying database is a pretty old idea.
https://docs.microsoft.com/en-us/dotnet/api/system.data.datatable?view=net-6.0 https://docs.microsoft.com/en-us/dotnet/api/system.data.data...
https://doc.qt.io/qt-5/qsqltablemodel.html https://doc.qt.io/qt-5/qsqltablemodel.html
Am I missing something novel in the article? I really feel like I'm missing something.
- hackerfromthefu 5y agoI agree with your assessment, and it's just the younger generation catching up to older established wisdom. The tragic irony is how hard many of that generation badmouthed the old ways of doing things. For instance ADO.NET with datatables/dataviews was often looked down upon, but through working more with people who did so it turned out that they just didn't understand it, so often that it's basically ten times out of ten.
- ripley12 5y agoHow is DataTable an example of that? It’’s a class that’s usually used to hold the contents of a relational database table, nothing to do with UI.
- intrepidhero 5y agoBecause you usually link it to a DataView and then the DataView updates when the underlying data changes. Same for QSqlTable, it links up with a QTableView.