Hi,

I created a new Q4 2024 (SVG Icons) Kendo Default Theme.

When I try to apply any of the provided color swatches, I see a loading spinner for 30 seconds and a "Failed to save document" error.

When I checked the network requests, I noticed that PATCH https://themebuilderapp.telerik.com/api/v1/projects/67a267df70e5e715ec193d0e/variables method returns 500 Internal Server Error with "Transaction with { txnNumber: 11 } has been aborted." error.

Consider exposing a template or a component part for the DateTickerPcker > Time > Highlight part.

The styling option is similar to what ThemeBuilder currently has for the TimePicker template

 

requested through t.1676966

Hi Team,

I encountered an issue while exporting a few selected components from the theme build. When I use them in my application, I’m seeing variable-related errors in the index file.

Please refer to the screenshot below:

In the screenshot, you can see that I have not exported the AppBar, Badge, and BottomNavigation components. However, their variables still appear in the index file.

I’m currently using:

kendo-theme-material": "^10.1.0"

Kindly look into this issue.

Thanks

Consider and research the options for automatically exporting and mapping styles from the Telerik UI Kits to the built-in Telerik/Kendo templates in ThemeBuilder.

Currently, when using Telerik UI Kit alongside the Figma plugin for ThemeBuilde, one can do one of the following:

- Export only the styles *& variables and then manually map the styles in ThemeBuilder

- Export and create custom components, which won't be connected to the Telerik/Kendo components and will have a custom HTML rendering.

 

Consider adding a functionality that will allow the bulk export of component variants in Figma while using the Figma plugin for ThemeBuilder.

For example, an option to export and create all variants of the Button in the Telerik UI kit

We recently upgraded our theme builder to ultimate so we could migrate our theme builder project from R1 2023 to Q4 2024. After we did this there were some small changes we needed to fix but after that we followed all the normal installation procedures.

We are running angular 18 and have updated all kendo components to the latest versions.

After installing the new theme we also added/changed the way we imported the theme package following the documentation (using @use).

Most everything looks good but there is one large issue with several of our components and that is the kendo theme mixin  "k-color" is not working.

In several places there is no color or background color being set on the component(s). When i inspect the style i see     color: k-color(primary); is not working. dev tools states that the variable is wrong. i can only assume the mixin is not imported/being used.

Image of my description

When exporting only selected components, it would be incredibly beneficial if ThemeBuilder could automatically generate separate override files specifically for those components. This approach would keep the codebase more modular, improve performance, and better serve applications relying only on certain Kendo components.

Requested through 1674517

With Kendo theme version 8.0.0 the some radius variables like $kendo-border-radius were removed and are no longer present.

Instead, there is now a new feature called kendo-border-radii that automates the creation of different border-radius variables (e.g. like $kendo-border-radius-sm aor $kendo-border-radius-lg)

More about the new variables in Kendo Themes 8.0.0 and above are available in the official documentation:
https://www.telerik.com/design-system/docs/themes/theme-material/theme-variables/#variables 

Consider exposing border-radius variables as they were present in older version but are not accessible in TB Q3 2024.

I modified a theme this morning and after changing a property got the error: "There are errors in SASS and it cannot be compiled to CSS.". Changing the property back to what it was before did not resolve the problem. Clicking the Undo button over and over and over did not resolve it. 

I started over with a backup taken yesterday and started reapplying changes. When I clicked "Export All" I once again got the same error. There is no way to recover from it. 

I've had ThemeBuilder licensed for some time, but this is the first week I've tried to use it in our application. It seems to be total garbage. I can't see any why forward with us using a tool that's going to randomly produce unrecoverable errors. 

 

Currently, there are no templates for modifying the sort icons of the filter cells of the TreeList component. There is a template for the Filter Row, which refers to the Grid component. However, the part with the sort icon is not connected to the Grid, as modifying it there doesn't reflect the change in the TreeList.

Consider exposing a templates for these icons.

We use the "/" method of organizing our variables, nesting them into (sub)categories. When we got to the Generate Names step, we needed to check about ~400 checkboxes individually to include/build their full names. I know we'll only need to do this once (unless you run into errors at the end a bunch of times like we did, requiring us to retry many times), but it would be a nice convenience to have a "Check/Select All" option at the top.

The Progress ThemeBuilder currently has the Fluent theme (by Microsoft), but only the light version is available.

As for the other themes (kendo, bootstrap, material) would it be possible to have the dark version too?

Thank you,
best regards

Roberto

Currently, we have templates for the different states of the Calendar cells:

However, it's common to apply multiple states simultaneously. For example, the user may want to style a day cell that is considered current and selected or current, selected, and hovering at the same time. Consider exposing templates for the most commonly used combinations, such as the ones mentioned here.

 

Requested through t.1670882.

In ThemeBuilder Q1 2024 there are Grid templates for styling alternate rows and selected rows. However, there is no template for styling selected alternate row.

Consider providing templates for each rendering option.

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

Sometimes, when using the Export Font Icons functionality of the ThemeBuilder Plugin for Figma, the export freezes with "Sending data to server: 0%":

This is due to how Figma handles the export of icons.

Consider implementing a mechanism for indicating the problematic icons so that users can remove/update them and make them eligible for export.

 

Starting from Q2 2024, new variables were introduced in the Kendo themes, such as primary-subtle, primary-subtle-hover, primary-subtle-active, etc., and they're all variants of some base color variable (e.g., primary).

Currently, if users choose to use a different hue for such base variables, they must manually change all of their variants as well.

Consider implementing a feature allowing users to change all variants of a variable based on an internal algorithm when the base variable (e.g., primary) is modified.

There is a template in the Constructive Elements canvas of components, such as Grid, MultiSelect, etc., for Filter List Item. Currently, ThemeBuilder does not have an exposed component part for modifying its search icon. It becomes problematic when we use font icons, especially a different font file for the icons, which requires changing the character code.

Consider exposing a component part to modify this icon.

Sometimes, errors occur in ThemeBuilder due to various reasons.

Consider including indicators in these errors to let the users know where they are located so they can possibly fix them through ThemeBuilder's user interface if applicable.

Requested through t.1667194.

In Sass is possible to define à variable like this

$primary: red;
$primary-filter: rgba($primary, .5);

But this possibility is not supprted by ThemeBuilder

It may be usefull for variation of same color in theme whit only one variable to adjust.