KendoUI vs Telerik Architectural Difference

I am developing an ASP.NET application for web api and am using kendoUI for the client side. I recognized this blog post that describes the differences between KendoUI and Telerik, but it does not reflect any architectural differences between the two. Is there a big difference in these two user interface interfaces in terms of architecture, which can lead to differences in performance? I am curious to know the difference in depth and why the Telerik team decided to come up with a new solution like KendoUI.

+5
source share
1 answer

We used to have what we called Telerik Extensions for MVC. Telerik extensions have simplified some of the UI's efforts in that they will output HTML, but developers are allowed to use some helpers to create common controls. E.g.

<%= Html.Telerik().Calendar()
            .Name("Calendar")
            .Value((DateTime)ViewData["selectedDate"])
            .MinDate((DateTime)ViewData["minDate"])
            .MaxDate((DateTime)ViewData["maxDate"])
            .TodayButton("d")
    %>

The code will display calendar control ui when rendering on the client side. This is the basic foundation of any server-side dynamic content creation technology such as ASP.NET, JSP, PHP, etc. Client HTML is actually spitting from the server when a request is made for this page.

Kendo, HTML5 JavcaScript, , . - Kendo UI, , , , , AJAX , , JSON . .

<div id="calendar"></div>
<script>
 $(document).ready(function() {
                    // create Calendar from div HTML element
                    $("#calendar").kendoCalendar();
                }); 
</script>

, .

- Kendo UI ASP, NET MVC Wrappers - - Telerim MVC - Kendo UI. ,

@(Html.Kendo().Grid<Product>()
    .Name("Grid")
    .DataSource(dataSource => dataSource
        .Ajax()
            .Read(read => read.Action("AjaxBinding_Read", "Grid"))
    )
)

- kendo ui .

Telerik MVC - Kendo UI. , Kendo UI Controls, HTML5, .

, .

( , )

+11

All Articles