Happy to elaborate.
I’m currently building a quasi-front end for an “app” in Coda. In this case, users would be directed to a specific section where only buttons specific to them would appear. In another section would be a table containing a button column. For example, the table may look like this:
And the “front end” section may look like this:
As you may have surmised, the IncreaseQuantityButton increases the quantity in the respective row, and the PurchaseDateButton resets the Date of Last Purchase Column to Now(). The MasterButton presses both button in the row, and performs as desired - only the buttons in the specific row are pressed.
I am trying to avoid having a table in the “front end” section. The buttons in the frontend section - ideally - would press the MasterButton in the corresponding row. e.g. The Bought a button would only press the MasterButton in the Hammer row.
There are certainly workarounds, and I have included some below:
I can create a table view of the MasterButton column and filter out rows that are not needed. This is not something I love since it creates an additional vector from which the table can be modified.
I create a separate table for each item. This is possible, but adds a lot of extra manual work and clutter.
I have the control buttons do what the buttons in the column are doing. This again is possible, but like #2, creates significantly more manual work and potential for error.
While this hypothetical use case does not exactly reflect my potential use case, the barriers are the same. It would not always be possible/practical to disable the buttons that I do not want pressed. I realize some of these issues are tangential to a granular permission system, and that Coda is still in beta (albeit, an impressive beta). I also want to make clear that I really enjoy Coda, and I appreciate you taking the time to discuss.