Revamp binding editor - Githubissues

mui / toolpad

Toolpad: Full stack components and low-code builder for dashboards and internal apps.

https://mui.com/toolpad/

MIT License

1.31k stars 293 forks source link

Revamp binding editor #1810

Closed prakhargupta1 closed 8 months ago

prakhargupta1 commented 1 year ago

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡

[ ] When I open my binding editor I sometimes forget which component am I editing, it would help if we show component name here in the title:

[x] The highlighted blue-box instead of component type, should also have the component name. Text1 in this case:

Janpot commented 1 year ago

For 2. shall we replace the component type with the component name? Can you benchmark what other tools do here?

prakhargupta1 commented 1 year ago

For 2. shall we replace the component type with the component name? Can you benchmark what other tools do here?

Checked appsmith, retool and superblocks and they all show the component name.

Janpot commented 1 year ago

For 1. there are some considerations

What about binding editors that are not on page elements? e.g. in the query editor
Suppose we make this editor less dialog-like and tie it closer to the property control visually, like we did with the datagrid columns editor. Would that add enough context to solve this problem?

For 2. I'm opening https://github.com/mui/mui-toolpad/pull/1818

prakhargupta1 commented 1 year ago

I think 2 would be the best approach as it leads to a more integrated and contextual UX. Let's try to solve it that way, I am adding design:UX label for further exploration.

prakhargupta1 commented 8 months ago

Marking it closed as we have started showing 'property name'. It gives the needed context.