All controls (such as TelerikGrid, TelerikDropDownList, etc) should have a "Visible" property. This bindeable boolean value controls whether the control is visible on the page or not:

<TelerikGrid Visible="@IsVisible" />

@functions {

protected bool IsVisible

}

This is a much better method than surrounding the entire control's markup in an @if(IsVisible) block, since that causes the control to get removed/added to the dom at runtime. This can cause many issues such as the control's constructors being fired multiple times, the dom getting "jiggled" about unecessarily.

I feel the "Visible" property is a cleaner way to hide controls.

When following the Blazor UI code examples for the Grid, the source for index.cshtml contains the following:

@page "/grid/index"

@using Telerik.Blazor.Components.Grid
@using TelerikBlazor.Shared
@inject HttpClient Http

Notice that the using directive for the Shared component doesn't have a . separating Telerik and Blazor. It should read:

 

@using Telerik.Blazor.Shared

For example we have built a web application using ReactJS which uses video and phone API capabilities from Twilio. If there are built in blazor components, application development becomes easy. 

Hello Team;
Hope you're enjoying your well-deserved holiday.

As the new features arrive, the new/update docs will be arriving too. In order for us to stay on the top of all the changes taking place on the Doc section, I'd like to suggest to have a page that each line contains:
a) Date
b) Doc description
c) A link to that section

This way, we can regularly look at this list and jump to the new docs to stay up to date with the team.

Thanks!
..Ben

Hello Team;

The current Blazor demo, runs as a client that is being hosted by a server side project. In the client project under wwwroot folder, there is an index.html there that acts as Blazor loader, with a fancy CSS animation and etc.

My suggestion for the RTM version of Telerik Blazor is to have something similar to this index page the we can use in out application that we can customize it a bit more.

I see a series of script files and links that many not needed for our apps.
It's just a thought and hope it can be done.

Thanks!
..Ben

I would love to see this UI control for blazor with all the same great features

• Filtering/Searching
• Templates
• Grouping
• Cascading

I have been playing with UI for Blazor a bit have have some minimal code working. I was wondering if is any rough documentation that at least lists the available attributes for KendoGrid, KendoGridColumn, RowTemplate, etc. Intellisense isn't popping up anything so I can't find what attributes are implemented. I know of KendoGrid: Data, Height, Sortable, Pageable, PageSize, and Page from the sample projects. For KendoColumn I am only aware of the Field attribute.

I'm not looking for detailed docs, as this is a very early preview, but if there is any way to at least find the names of the possible attributes, then I may be able to figure out how to use them myself.

Thanks and keep up the good work