Coda Feature Request: Add Tabbed Layouts to Row Detail Views

row detail views desperately need a tab feature for switching between layouts.

something like the current implementation for tabbed views would be great:

…but, you know, without the nested table inside of a canvas and whatnot.


yes, i know i can use OpenRow() buttons to make them, and have done so:

however it has big disadvantages:

  • it requires lots of formulas for the buttons and their actions
  • it’s forgotten each time the row is opened normally (Expand Row, clicking the card, etc.)
    • you can add a button with a ModifyRow() action that saves the current tab to a column, BUT that:
      • requires two extra columns — one for the button itself, and one for saving the current tab
      • overwrites it for all users
      • requires button() which is both harder to code and incredibly fragile
      • is too easily bypassed by opening the row normally
      • requires complicated formulas for the button to both write and read the current setting
    • you can have ModifyRow() write to a personal control instead, BUT that
      • STILL requires complicated button formulas
      • requires a separate control for each table or set of views
  • each tab requires a separate button, which takes up a lot of space
    • you can use button() to merge them into a single column, BUT that’s
      • way harder to configure than a normal button
      • requires button() for each tab (again, harder to code, incredibly fragile)
  • needs to be set up repeatedly for each table
  • OpenRow() doesn’t let you select a layout directly — instead, you have to pick a VIEW with that layout assigned to it. why???
  • OpenRow() overwrites the user’s viewMode setting (Fullscreen/Right/Center/etc.), even if left blank! why doesn’t it just fallback to the user setting???

i’m also aware you can embed a linked relation with a Detail View to switch between canvasses with embedded layouts:

but this:

  • requires a whole separate table just for the layouts
  • requires “template rows” with their own pre-designed canvases that get duplicated for each new row
  • requires a button to duplicate and modify those template rows
  • requires doing so for each new row in your main table
  • if you change one canvas, you now have to retroactively change every other version of that canvas to match (or create a button to regenerate template rows for every dang table)
  • it’s literally a detail view inside a canvas inside a detail view inside a detail view, which is crazy work
    • look at how tiny that embedded detail view is. the width is terribly constrained by all the padding from the nested table views.

so yeah, please introduce this feature natively, p l e a s e

3 Likes

This is a very well thought-out and detailed feature request.
Well done.

I vote for this!

Except I cant - because I have used up all my votes and cannot seem to get any more ?? !!

@Ruggy_Joesten1, any chance of resetting our voting limits so we can VOTE on things?

Max

4 Likes

Letting the cat out of the bag a little early, but be ready for a nice update here with the forum refresh

3 Likes

Hello @Ruggy_Joesten1

Regarding the forum UI refresh: is it planned or possible to turn the “Suggestions” category into a more Canny-like interface, where each suggestion would be clearly tagged by Coda as “Nope,” “Under review,” “Planned,” “In progress,” or “Done”?

I genuinely believe this would improve transparency and communication with the community. As it stands, most topics in this category seem to lead nowhere. I mostly see community champions stepping in with great answers and thoughtful workarounds, but very little input from Codans.

As a Coda lover (who now needs concrete releases more than announcements to rebuild confidence), this kind of change would feel like a clear and welcome cultural shift :+1:

5 Likes

sorry, could you clarify, is this update related to votes, or is it related to my feature request?

1 Like

Apologies for the delayed response!

I don’t believe this can be built natively on the Discourse platform, but I’m planning to put together a doc to consolidate all the feature requests we’ve received, including the great suggestions that came in before I joined, so nothing gets lost. From there, my hope is to find ways to keep the community looped in as these ideas move through the roadmap process.

2 Likes

Votes! We hope to never again be burdened by the oppressive systems holding us back from freely engaging on the forum :flexed_biceps: :ballot_box:

1 Like