Currently the components accept only ClientTemplates. From an ASP.NET perspective it is more convenient to store the templates in ~Views\Shared\DisplayTemplates folder.
Please provide a new method TemplateView("ViewName") that will look for the partial in the folders much like we have it for the EditorTemlates.
Hi Telerik Team
We think it might be very useful an component in telerik like this one https://fengyuanchen.github.io/cropperjs/ for rotate, crop, resize, zoom and move. with a picture box like https://ashleydw.github.io/lightbox/#videos-gallery
If you implement this we will very happy
Thank you
kendo.aspnetmvc.js does not account for server aggregates serialized with came case property names like it does for Groups.
Can the following code (minus the comments) be included in a future release to resolve this?
function translateAggregateResults(aggregate) {
var obj = {};
// LSS: support for camel case serialization
obj[(aggregate.AggregateMethodName || aggregate.aggregateMethodName).toLowerCase()] = (aggregate.Value || aggregate.value);
return obj;
}
function translateAggregate(aggregates) {
var functionResult = {}, key, functionName, aggregate;
for (key in aggregates) {
functionResult = {};
aggregate = aggregates[key];
for (functionName in aggregate) {
functionResult[functionName.toLowerCase()] = aggregate[functionName];
}
aggregates[key] = functionResult;
}
return aggregates;
}
function convertAggregates(aggregates) {
var idx, length, aggregate;
var result = {};
for (idx = 0, length = aggregates.length; idx < length; idx++) {
aggregate = aggregates[idx];
// LSS: support for camel case serialization
result[(aggregate.Member || aggregate.member)] = extend(true, result[(aggregate.Member || aggregate.member)], translateAggregateResults(aggregate));
}
return result;
}
extend(true, kendo.data, {
schemas: {
'aspnetmvc-ajax': {
groups: function (data) {
return $.map(this._dataAccessFunction(data), translateGroup);
},
aggregates: function (data) {
data = data.d || data;
// LSS: support for camel case serialization
var aggregates = data.AggregateResults || data.aggregateResults || [];
if (!$.isArray(aggregates)) {
for (var key in aggregates) {
aggregates[key] = convertAggregates(aggregates[key]);
}
return aggregates;
}
return convertAggregates(aggregates);
}
}
}
});
Be able to bind the DataSource to data without a separate controller and AJAX fetch for use with Razor Pages.
The use case is a shared data source that drives multiple components on a page for example a chart and grid filtered with an auto complete box.
In a grid I can do this:
@(Html.Kendo().Grid(Model.Data)
.Name("Grid")
.Columns(columns =>
{
columns.Bound(p => p.Description).Title("Description");
columns.Bound(p => p.RecordCount).Title("Number Sold").Width(130);
columns.Bound(p => p.TotalValue).Title("Total Value").Width(130);
columns.Bound(p => p.AverageValue).Title("Average Value").Width(130);
columns.Bound(p => p.Rank).Title("Rank").Width(130);
columns.Bound(p => p.RankMax).Title("Bananas").Width(130);
columns.Bound(p => p.LowerQuartile).Title("LowerQuartile").Width(130);
columns.Bound(p => p.Median).Title("Median").Width(130);
columns.Bound(p => p.UpperQuartile).Title("UpperQuartile").Width(130);
})
.Sortable()
.DataSource(dataSource => dataSource
.Ajax()
.PageSize(20)
.ServerOperation(false)
)
)
Would want to be able to do same with the DataSource like:
@(Html.Kendo().DataSource(Model.Data)
.Name("dataSource1")
.Ajax(dataSource => dataSource
.ServerOperation(false)
)
)
Bug report
The StringExtensions -> ToCamelCase method(part of Kendo.Mvc.Extenstions) doesn't return the expected Camel case result.
- More details in ticket # 1458202
Reproduction of the problem
Include the Kendo.Mvc.Extenstions namespace. Define the following in a controller:
public IActionResult Index()
{
string test = "RANDOMStatusId";
test = test.ToCamelCase();
return View();
}
Set a debugger and see the value of the "test" variable.
Current behavior
The returned from the ToCamelCase() method value is "rANDOMStatusId"
Expected/desired behavior
The expected result returned from the ToCamelCase() method value is "randomStatusId"
Environment
- Kendo UI version: 2020.1.219
- jQuery version: x.y
- Browser: [all]
Even when using server side paging some requests can be very long, and may be canceled by the user. Adding a CancellationToken parameter to the ToDataSourceResultAsync.
Bug report
Validation attributes are not rendered on Kendo editors if ViewData contains same key as the model.
Reproduction of the problem
@{
ViewData["Title"] = "Home Page";
}
@using (Html.BeginForm())
{
@Html.Kendo().TextBoxFor(model => model.Title)
}
<script>
$(function () {
$("form").kendoValidator();
});
</script>Current behavior
Validation attributes are not rendered.
Expected/desired behavior
Validation attributes should be rendered on the input element.
Environment
- Kendo UI version: 2020.1.219
- Browser: [all]
The Menu TagHelper does not render correct links for its items when the asp-page attribute is used.
With area it does not render a link at all:
<menu-item text="Home" asp-area="Products" asp-controller="Home" asp-action="About"></menu-item>
Without area it renders an incorrect link
<menu-item text="Login" asp-area="Products" asp-page="/Books"></menu-item>
When a model property is decorated with data annotation attributes, the RadioButton HtmlHelper does not properly render the data-val and data-val-required attributes on the element.
Expected behavior: Data attributes should be successfully rendered on the <input> element.
I am looking for an extension to the Grid Columns fluent api that adds .Exportable(true or false). Exportable(true) would be the default and indicate that this column does get exported when exporting to Excel (or PDF). Exportable(false) would indicate that the column does NOT get exported.
Imagine the following Grid Definition:
@(Html.Kendo().Grid<Services>
()
.Name("gridMain")
.Columns(columns =>
{
columns.Bound(p => p.ServiceId).ClientTemplateId("rowNumTemplate").Title("Row").Width(50);
//columns.Bound(p => p.ServiceId).ClientTemplateId("cmdsTemplate").Title("Cmds").Width(125).Media("(min-width: 768px)");
columns.Bound(p => p.ServiceCode).Media("(min-width: 768px)");
columns.Bound(p => p.ServiceId).ClientTemplateId("xsTemplate").Title("Service / Desc / Code").Media("(max-width: 768px)");
columns.Bound(p => p.ServiceId).ClientTemplateId("serviceTemplate").Title("Service / Desc").Media("(max-width: 992px) and (min-width: 768px)");
columns.Bound(p => p.ServiceName).Media("(min-width: 992px)");
columns.Bound(p => p.ServiceDescription).Media("(min-width: 992px)");
columns.Bound(p => p.ServiceActive).ClientTemplateId("activeTemplate").Width(60).Media("(min-width: 768px)");
columns.Bound(p => p.ServiceId).ClientTemplateId("btnsTemplate").Title("View/Edit/Del").Width(150);
//columns.Bound(p => p.ServiceId).ClientTemplateId("xsCmdsTemplate").Title("Cmds").Media("(max-width: 768px)");
})
.Scrollable(scrollable => scrollable.Endless(true))
.Pageable(p => p.Numeric(false).PreviousNext(false))
.ToolBar(t => t.Search())
.Search(s => { s.Field(c => c.ServiceCode); s.Field(c => c.ServiceName); s.Field(c => c.ServiceDescription); })
.Resizable(resize => resize.Columns(true))
.ToolBar(t => t.Excel().Text("Excel"))
.Excel(excel => excel
.FileName("ABT_Services.xlsx")
.Filterable(true)
)
.DataSource(dataSource =>
dataSource
.WebApi()
.PageSize(Model.GridPageSize)
.Model(model =>
{
model.Id(p => p.ServiceId);
})
.Events(events => events.Error("errorHandler").RequestEnd("gridMainRequestEnd"))
.Read(read => read.Action("Get", "Services"))
)
)What I would like to do is define a column like the following:
columns.Bound(p => p.ServiceId).ClientTemplateId("rowNumTemplate").Title("Row").Width(50).Exportable(false);
In the case above, the "Row" column would not be Exported to Excel.
If you take a closer look at the Columns definition above you will see that the configuration is implemented to support responsive page sizing. Because the current implementation of Export to Excel does not allow an Exportable(true/false), I get these columns that I don't want in the exported Excel.
Although there appear to be workarounds (like keeping a second hidden grid -- a poor solution at best), none would be as useful to a Developer as defining an Exportable(true/false) as part of the Column configuration.
Thanks for considering my request.
I`m working development and produced I4.0 devices as well app systems since 3 years. Are Telerick involve in this applications.
Hello,
We want to create a custom Material theme for our ASP.NET Core web application. We are using the Sass Theme Builder but can only select predefined color swatches for the "Material" base theme. We would like to be able to set custom colors per "subject" just like you can with the "Default" and "Bootstrap" theme.
Is this possible or are you blocking this on purpose for some reason?
Thank you in advance.
Hi, Any plan to release asp.core with angular 2 template like mvc5 with angular .
I want to design a web page with text and signature input. In Tablet I need to enter the text fields and signature fields using touch pen. I want the web page to allow the touch pen to write comments and signature and save into database
I have a donut chart which represent as a circle and in middle of cricle there is some text, which needs to drilldown, hence click event need which is very necessary
Need support for DataTable in Grid in ASP.NET Core 2.0
Allow general configuration of SuggestionOperator, as is available for Operators.
I can do something like this in GridFilterableSettingsBuilder --
filterable.Operators(operators => operators
.ForString(str => str
.Clear()
.Contains("contains"))I would like to also be able to do this --
filterable.SuggestionOperator(FilterType.Contains)