sumob11892Q: Hi, Trying to understand Grist, it is somehow the equivalent of database "backend".
This "backend" can stay private or can be exposed on "frontend" either full or only pre-selected data (specific rows/columns etc)
"Frontend" can also be displayed via widgets (that grab data from database).
Up to here, please correct if anything wrong :)
Now, questions:
a) Are widgets showing only one piece of data at once (one row) or can a widget display multiple (pre-selected) rows and columns (eg. a big but good looking table)?
b) Can a widget also accept data input from users?
As in, see the nice table, but also edit right there move cells or add new rows etc. (?)
Thank you.
Anais-Grist
May 15, 2024A: Grist is helping you build a relational database through a familiar format, the spreadsheet. So the front end is also a database, it just feels more like interacting with a spreadsheet (because it is, also, a spreadsheet đ)
As for your questions,
a) Widgets can display multiple preselected columns and rows. Widgets can also be filtered individually. Say you have Widget 1 and Widget 2, both are views of data in Table A, the widgets may have different filters and sorting options, and different shown v hidden columns.
b) Yes, widgets are ideal for simplifying data entry. For example, instead of filling in a row that scrolls horizontally across 20 columns, you may present the data as a card which makes data entry feel like filling in a form. The one exception to this is summary tables (analogous to pivot tables) that summarize data in key figures. Summary tables are new tables and data entry in a summary table will not enter data into the underlying table that is being summarized.
The best way to get a grasp on this is by playing with Grist! You can play with Grist, with or without an account, at docs.getgrist.com .
This video also helpfully explains pages and widgets: https://youtu.be/vTfOUEFR73Y