It would be helpful to add a feature to ThemeBuilder that allows users to create theme variable modes based on typography variables, similar to the existing feature that lets them create themes based on color and metrics.
This will enable users to generate different themes within a single project by simply changing the fonts used.
Requested through t.1656320
Currently, in ThemeBuilder there is a template that allows you to style the icon of a header cell that is filterable.
However, we need to be able to style the icon in a header cell that triggers the ColumnMenu (the more icon)
https://demos.telerik.com/aspnet-core/grid/column-menu
https://www.telerik.com/kendo-react-ui/components/grid/interactivity/column-menu/
requested through t.1655985
Currently, in ThemeBuilder, you can't style DropDownList, which uses groups.
https://demos.telrik.com/kendo-ui/dropdownlist/grouping
https://www.telerik.com/kendo-react-ui/components/dropdowns/combobox/grouping/
Consider the option to expose a template that will allow adding custom styles for DropDownList with grouping.
Requested through t.1645162
I need to be able to enter `rem` (or even `em`) values for metrics like `padding`.
Hello.
One of our component is styled in a way that makes it indistinguishable from the background, which is unfortunate and makes hard to review its visuals.
Could you add support for selecting different background in previews? Something like gray shades or a pattern?
Consider exposing a ThemeBuilder template for the Popup component.
https://www.telerik.com/kendo-react-ui/components/popup/
https://docs.telerik.com/kendo-ui/controls/popup/overview
https://docs.telerik.com/blazor-ui/components/popup/overview
https://www.telerik.com/kendo-angular-ui/components/popup/
https://github.com/telerik/kendo-themes/blob/develop/tests/popup/popup-no-data.html
When an element is selected in ThemeBuilder, it shows its Parts and Properties on the right and a Live Preview at the bottom. I would really benefit from seeing the HTML code/markup (snippet), e.g. `<button kendoButton themeColor="primary" fillMode="flat">Button</button>`. I'm trying to decipher what attributes I should be using by looking at the applied classes, but it's not always 1-to-1 or clear.
Steps to reproduce the bug
In Themebuilder:
Expected behavior : The two different values should be persisted and applied.
Actual behavior : The behavior is strange and editing one value seem to overwrite the other.
Hello,
The MultiSelect and ComboBox Icons seem to have issues. First, in the MultiSelect, I'm not able to customize the icon within the IconButton. In the similar ComboBox, I can customize the icon, but the change is not reflected in the live view.
I would expect that all the clear "X" icons within the dropdown components would inherit from the base TextBox "Clear Icon" but they don't.
Regards,
Brian
When the ThemeBuilder project has custom variables or variables exported from Figma in the output _tokens.scss file all variables are with the ‘tb’ or ‘figma’ prefix.
It will be good if these prefixes can be configuration options for the project and users can choose what prefix (or no prefix) should use.
Consider providing partial exports for the SCSS when working with the Kendo Fluent theme. Partly exports are available for all other flavors except for the Fluent theme.
+1 from t.1652071
In my example the neumorphism-default
box-shadow: 3px 3px 5px 0px rgba(52, 178, 50, .33), -3px -3px 5px 0px rgba(255, 255, 255, .6);
On the ButtonGroup I got overflow on the other buttons and I want to clip the buton for remove the shadow on adjacents buttons.
In my example:
This clip-path can help to apply shadow on the buttons group
to pass from this :
to this
Hi,
Would it be possible to expose either a "before" or "after" selector on Treeview Root/Child items?
This would allow an additonal hook for styling, and it a feature of items in the Drawer, Panelbar etc.
Many thanks,
Ian
Currently, the ThemeBuilder application supports only major Kendo releases (like R1, R2, and R3) and the version of the theme that is interconnected with these release versions.
Consider the option to provide functionality to choose between newer versions of the Kendo themes that are released with service packs and patches. This way, the user will have the ability to test versions that contain theme fixes before the next major release.
For example, R2 2023 officially supports Kendo theme 6.4.0, and before R3 2023 is released the Kendo theme is already at version 6.7.0
Consider the option to support absolute paths for background-image in the Style Editor.
This will enable users to visualize the background-image changes directly in ThemeBuildeer (currently the only option is to export the theme and load the changes in the end application).
Alternatively, consider the option to provide a space for loading images with relative paths (fir fast preview in ThemeBuilder).
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!
Add a new smart code editor as a variant of the Property Grid with all visual properties. Do not replace the property grid with this editor. They can live next to each other in different tabs. The smart code editor should support all features of the property grid but with advanced functionalities.
1. Show all kendo styles attached to the selected layer in a text format
2. Marks which style is overridden by user styles
3. Users can add any CSS property, not just the one listed by the Proprty grid editors.
4. Intellisense for CSS properties, something like:
5. Intellisense for using sass/css variables – the editor can recognize the property name and list only corresponding tokens for example – background – shows color tokens, box-shadow – shows effect tokens. Something like: