Introduce a way to style the SearchBox of the Grid component.

I am wanting to change the padding on all components on a Bootstrap theme. The defaults appear to be .375 rem X .75 rem. I would like to change all components that have those theme settings to a custom number. Is there any way to do it beside selecting one component at a time and working down through the list? 

I would like to be able to set the style for the focus state for all the input controls in one place.

Currently I would need to select each control, go the advanced edit and set my style. If I then need to make a small change to that style I have to repeat the process for each individual component.

It would be useful if there was a selector on the title bar of each component group that allowed you to set a styles for all the components in the group for states such as hover, focus etc.

Add ability to style the table headers in Scheduler

Add support for all possible Button variants and configurations in ThemeBuilder. This includes all possible variants for: 

• size
• shape
• rounded
• fillMode
• themeColor

How do you set separate padding for different size buttons? I want to make use of the small, medium, large sizes available in the toolkit, but in Themebuilder, it seems there is only one size button

Hello. We'd like the pager to behave in such a manner so that when the user mouses over the selected button it stays the same color etc. instead of changing to the hover state. So if that means adding a Selected-Hover State to the Pager, that would be much appreciated.

Is there any thought on reintroducing the possibility to export a storybook instance from themebuilder pro as there was in Unite UX. Would be very nice to have a place to explore the KendoUI components with our own theme!

Hello,

Could you please add editable states to the PanelBar > Child Item Level 2, so that it can have a proper indent?

Thanks

How would I add custom tokens e.g. different shadow settings in ThemeBuilder. 

 

This is the JSON for one such setting:

    "$gph-grey-100": {
      "value": "#8f8f8f",
      "type": "color"
    },
    "$gph-shadow": {
      "value": {
        "x": "3",
        "y": "04",
        "blur": "0",
        "spread": "0",
        "color": "{$gph-grey-100}",
        "type": "innerShadow"
      },
      "type": "boxShadow"
    }

Hi,

Currently, ThemeBuilder Pro is not supporting ASP.NET AJAX.

So, we would like the ability to create theme for ASP.NET AJAX.

Thanks,

Hello,

I am noticing that there are several styles that we cannot access through ThemeBuilder such as adding transitions, custom icons, etc. We would like the ability to export the ThemeBuilder package, add custom styles, then import back into ThemeBuilder. Is this possible? If not, this would be a great feature.

Thanks!
Ian

Hi,

Inside the exported zip from ThemeBuilder is a npm package, and I noticed that the package version is always set to 1.0.0.

Is there a way to edit and/or auto increment the package version so we can publish the exported themes to our internal npm repository?

 

Hello,

We have been creating custom variables for a color palette that our design system uses. However, we are unable to set any of the global properties (ie. text color) to one of the custom variables we have created. The list of variable options is limited to the "Theme Colors." We can set the color manually by setting the hex color it would be great if we could use our custom variables, especially if the list of global variables grows in the future.

Thank you for consideration of this feature!

Hello,

We are planning on setting many custom variables and would like more control over their ordering and naming.

• Enable sorting of custom variables
• Enable numbers in variable names

Thank you for your consideration!

Hello,

It would be great if Themebuilder had version control built into the tool so that our designers could view previous versions of the theme styles and revert back if necessary. Currently, we are planning on downloading the files and pushing to git, but this is very cumbersome.

Thanks for considering this!