Kevin Shenk

Results 64 comments of Kevin Shenk

@hj-collab are you insinuating that the @pressjitsu approach is now irrelevant?

I'm experiencing issues with this as well. In my case, components nested within a component are visible on the pages where they're present, but do not display the attribute overrides...

I just realized that components don't sync automatically, so that does dampen my enthusiasm for this...

A few more layout control inspiration screenshots from Cwicly: Flex layout parameters: ![image](https://github.com/frappe/builder/assets/4996285/e3d9afe0-eb8c-43fd-84c6-f85ffc3f2c20) Grid layout parameters: ![image](https://github.com/frappe/builder/assets/4996285/f73a9322-1796-4f9e-993d-e9bbd93d6f98)

I wonder if Frappe and Builder could be extended to enable apps to provide builder components that could help close this gap. I'm thinking the `frappe/payments` app could provide a...

Edit: I should have acknowledged that the color selector popup exists already and is off to a great start, but would ideally allow for selecting from a global color variable...

Edit: I just discovered that click-and-drag incrementing is already implemented! That's arguably better than scroll-to-increment.🤩 I suggest that keyboard incrementing be implemented as well.

Perhaps the existing work on the [visual query builder](https://github.com/frappe/insights/blob/develop/frontend/src/query/visual/VisualQueryBuilder.vue) in Insights could be harnessed here in some way.

Edit 2: Pure numeric inputs like the order field already utilize an input of type number, so all requested functionality is satisfied already: ![image](https://github.com/frappe/builder/assets/4996285/6fba7fe3-1b73-4a3e-890a-901b44b6e999) The issue is on inputs that...

This should include form elements as well, especially if/when there's a native webform integration block.