Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat]: Table Actions buttons #1519

Open
crrobinson14 opened this issue Feb 10, 2025 · 2 comments
Open

[Feat]: Table Actions buttons #1519

crrobinson14 opened this issue Feb 10, 2025 · 2 comments
Assignees
Labels
Components Dedicated to Frontend Visual Components Javascript Frontend Pull requests that update Javascript code

Comments

@crrobinson14
Copy link

Is your feature request related to a problem? Please describe.
Not a problem, more of a challenge - organizing busy user interfaces with a lot of tables.

Describe the solution you'd like
It's very common to want to add buttons to tables. The current option appears to be a custom column of type Button. This works for one button, but if you want 3-4 buttons and/or just don't want a big-screaming-button always visible in the UI, it gets busy fast.

Some table components in other solutions have a "Row Actions" option set at the table level. These are usually more subtle buttons shown in a smaller left- or right-aligned overlay when hovering over a row. That means they're hidden when not needed (less busy) and it's easier to set up more than one.

Describe alternatives you've considered
So far the Button type column is the only option I've found.

Additional context

Image Image

If you think this is the kind of task a newbie might contribute I'd be happy to take a poke, but I'm very new to LowCoder so I'm not sure I'd pull it off well.

@FalkWolsky
Copy link
Contributor

Did you explore the Dropdown Button Column Type? Maybe this could be helpful to organise a small edit menu per row?

Image Image

We understand that the customization options are too limited for the button and the interaction pattern of the dropdown is not exactly as you envision.

We see multiple ways to proceed and develop a better solution:

  • Add Event Handler Suppport to text column type - as there you could use a Icon already (prefix / suffix-icon)
  • Add better styling and Icon support for the Button column type
  • Add a new "actionbutton" column type focussing to your described function and esthetics.

What could you prefer and imagine?

@FalkWolsky FalkWolsky self-assigned this Feb 13, 2025
@FalkWolsky FalkWolsky moved this to 🆕 New in Lowcoder Feb 13, 2025
@FalkWolsky FalkWolsky added Javascript Frontend Pull requests that update Javascript code Components Dedicated to Frontend Visual Components labels Feb 13, 2025
@crrobinson14
Copy link
Author

It's a fair question. Currently we are using a Dropdown as you described above to work around this for now. Of the three options, it seems the cleanest, and is doable today with existing LowCoder functionality. It looks fairly nice and is pretty easy to use.

The downside it has (and the other options also share) is that it still requires an additional column. This means:

  1. The column takes additional width in the table, a challenge for wide tables.
  2. It is always visible rather than just being shown on a single row upon hover, so it looks "cluttered".
  3. It requires an additional click to display the menu and then select what you want to do.

If it wasn't clear from the original post above, the feature request here is for:

  1. An optional set of buttons that appear position: absolute to appear on TOP of the row rather than as an additional column, and
  2. To only appear on hover over the row, so it doesn't clutter up the UI when it's not about to be used.
  3. The buttons appear as a horizontal row, so unlike a dropdown they're immediately available with a single click instead of having to also open a menu.

That being said I'm having a doubt about my original request because I'm not sure how solutions like Retool are dealing with the hover aspect in mobile. That might introduce enough clumsiness that the whole idea is a bad one, so maybe the Dropdown with the ellipsis icon as you've shown is the best option anyway... 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Components Dedicated to Frontend Visual Components Javascript Frontend Pull requests that update Javascript code
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants