3 ms·

My first reaction (because you have a lot of stipulations) would be to use Drupal, which comes with views (a db query engine) in core. I am not up to date with

by prox 7y ago

My first reaction (because you have a lot of stipulations) would be to use Drupal, which comes with views (a db query engine) in core. I am not up to date with details, but it should be able to get you very far. I did a booking system that did some impressive queries very fast, and allowed data export.

simion314 7y ago
I think he mentioned that it must be 1 thing, no dependency, imagine he is already using soem other backend and now he has to switch to Drupal for a good Dratagrid and tomorrow when he needs a rich text editor he needs to switch to Wordpress and the new day when he needs a decent chart he has to use GWT. The ideal is that Web Technology would have built-in or if not community made building blocks. If made by community it must have no licensing issue, no dependency hell, no 100 alternatives for each widget. In my experience jQuery UI is the one that got close to this. You had only 1 dependency on jQuery, the community was not fragmented to have 100 alternatives for each thing and the included widgets are not incomplete.
- prox 7y ago
  The backend should be your database, and Drupal is one of the more successful CMSes that takes care of the model/view. You can build views very easily with them and use that as your search engine or table (or both), you can hook it up with its api for more flexibility if you so wish. I don’t know in this exact use case, but there are probably building blocks (modules) for his to get very close. I’ll absolutely agree Jquery is an excellent library that I use to this day. It’s extremely elegant and indeed, it is a good example how it is suppose to be done.
  - TeMPOraL 7y ago
    Well, if I have a backend serving views, then sky is the limit :). But I really meant a self-contained, fully front-end piece of JS. One you could feed a data table and let the user play with it. A side issue I'm hinting at is that I believe the features I mentioned should be present by default in any kind of tabular display. Without them, the users are getting shafted - they're served data in front of them (be it item prices, virus stats, or a restaurant menu), but they have no way to explore it on their own. This is but a small piece in a great set of ways in which our industry ensures the users can't ever grow and become more proficient, and then complains that users are dumb. Can't have a bicycle for the mind if pedals and handlebar are not provided.

by prox 7y ago

simion314 7y ago

I think he mentioned that it must be 1 thing, no dependency, imagine he is already using soem other backend and now he has to switch to Drupal for a good Dratagrid and tomorrow when he needs a rich text editor he needs to switch to Wordpress and the new day when he needs a decent chart he has to use GWT. The ideal is that Web Technology would have built-in or if not community made building blocks. If made by community it must have no licensing issue, no dependency hell, no 100 alternatives for each widget. In my experience jQuery UI is the one that got close to this. You had only 1 dependency on jQuery, the community was not fragmented to have 100 alternatives for each thing and the included widgets are not incomplete.

prox 7y ago
The backend should be your database, and Drupal is one of the more successful CMSes that takes care of the model/view. You can build views very easily with them and use that as your search engine or table (or both), you can hook it up with its api for more flexibility if you so wish. I don’t know in this exact use case, but there are probably building blocks (modules) for his to get very close. I’ll absolutely agree Jquery is an excellent library that I use to this day. It’s extremely elegant and indeed, it is a good example how it is suppose to be done.
- TeMPOraL 7y ago
  Well, if I have a backend serving views, then sky is the limit :). But I really meant a self-contained, fully front-end piece of JS. One you could feed a data table and let the user play with it. A side issue I'm hinting at is that I believe the features I mentioned should be present by default in any kind of tabular display. Without them, the users are getting shafted - they're served data in front of them (be it item prices, virus stats, or a restaurant menu), but they have no way to explore it on their own. This is but a small piece in a great set of ways in which our industry ensures the users can't ever grow and become more proficient, and then complains that users are dumb. Can't have a bicycle for the mind if pedals and handlebar are not provided.