06-18-2022, 09:48 PM
The kind of data-driven apps that (IMO) no/lo-code is well suited for have a number of common patterns.
One in particular is so common it's almost ubiquituous:
- an 'overview' page (either layout or table element) showing all/some of the records of a table.
- a button within the per-record part of that display which takes you to a view or edit page
- a button which adds a new record, and takes you to a page almost identical to the view or edit page above
It is wrong (IMHO) that you need to write *any* code at all to achieve this. There should be an option in the right-hand pane while editing a button which allows you to specify that this button changes screen (and gives maybe a drop-down of other screen to select which one to go to), and sub-options to indicate whether new record or the recordID of the current record in the layout.
On those lines, the sample app for contacts has 3 almost identical pages - add, detail and edit. As far as I can see, these have each been described (at some length), though they vary only very slightly (labels on the cancel/save/add buttons, whether or not the 'back' button is visible). There ought to be a way to share the commonality of the pages. For instance, if you decided to add a field (or rename a field like 'first name' to 'given name') you'd have to do it in multiple places.
So there's an additional tiny feature request - copy/paste screen.
One in particular is so common it's almost ubiquituous:
- an 'overview' page (either layout or table element) showing all/some of the records of a table.
- a button within the per-record part of that display which takes you to a view or edit page
- a button which adds a new record, and takes you to a page almost identical to the view or edit page above
It is wrong (IMHO) that you need to write *any* code at all to achieve this. There should be an option in the right-hand pane while editing a button which allows you to specify that this button changes screen (and gives maybe a drop-down of other screen to select which one to go to), and sub-options to indicate whether new record or the recordID of the current record in the layout.
On those lines, the sample app for contacts has 3 almost identical pages - add, detail and edit. As far as I can see, these have each been described (at some length), though they vary only very slightly (labels on the cancel/save/add buttons, whether or not the 'back' button is visible). There ought to be a way to share the commonality of the pages. For instance, if you decided to add a field (or rename a field like 'first name' to 'given name') you'd have to do it in multiple places.
So there's an additional tiny feature request - copy/paste screen.