1. Is it hard to understand the version numbers of our releases? If yes, what makes them hard to understand them?
2. Would semantic versioning (SemVer) of our releases make it easier to understand our version numbers and what's behind them?
3. If we go with SemVer, we might need to start with version 3000.0.0 as we currently use 2022.x.x. Please share your thoughts about this approach and ideas for what number versioning would work best for you.
Is it possible to conditionally show and hide items in a Kendo form based upon the data?
For example, if I have a form to enter a Person or a Company, I want to hide the Address field if it is a Company, or hide the Contact field if it is a Person.
Also please note that if attributes are used to try to set the field to display:none as in the example here., it only hides the editor, not the label or hint.
<form id="myForm"></form>
<script>
$("#myForm").kendoForm({
formData: {
Name: "John Doe",
Address: "123 Main St.",
Contact: "",
Type: 1 // 1 = Person, 2 = Company
},
items: [{
field: "Name",
hint: "Enter Full Name",
}, {
field: "Address",
hint: "Enter Address with ZIP Code",
attributes:{
// need to hide this field if the Type = 2
class: "person"
}
}, {
field: "Contact",
hint: "Enter the Company Contact",
attributes:{
// need to hide this field if the Type = 1
class: "company"
}
}]
});
</script>
<style>
.person {
display: block;
}
.company{
display: none;
}
</style>
I have a form where I want to use radio buttons to represent the item value, but I want the label of the radio buttons to be something different than the value. For example, I have a name and I want to distinguish that name between a type of Person or Company, but the data value representing the name type is numeric.
I can setup the form like this:
<form id="myForm"></form>
<script>
$("#myForm").kendoForm({
formData: {
ID: 1,
Name: "John Doe",
Type: 1 // 1 = Person, 2 = Company
},
items: [{
field: "Name",
validation: { required: true }
}, {
field: "Type",
editor:"RadioGroup",
editorOptions: {
layout: "horizontal",
items: [1, 2],
select:function(e){
// Do something here?
}
},
}]
});
</script>
Using Items: [1, 2] does work, but I don't want to show 1 and 2 on the radio buttons. I want to show Person and Company. How do I achieve that? Can I set Items: ["Person", "Company"] and then do something in the select function? If so, what needs to be done to set the model data correctly?
Please note that in my actual code, I am using setOptions for the model data, and not formData.
Thanks, Bob
Hi,
I have created .net core project and imported Kendo UI jQuery files from the given path and placed them in my project's js path along with trial license key .js file. But I need to invoke "kendo.all.min.js", "kendo-ui-license.js" using client-side library path for libman.json. If it is possible to invoke then please guide me with client-side library settings. And also let me know how to take the actual license instead of trial license.
Thanks,
Dhirendra
I've seen your demos on setting up the type: "date" and the format: stuff on the model and on the column display for the grid. Your demo sorts the dates as if they are dates properly. Ours shows the value as null if we set the type to date. It displays the string properly if we set it to type string but still sorts as a string. If we simply set the column to the kendo format and do not use a schema on the datasource, our code still sorts as a string.
https://dojo.telerik.com/TgCibbiL
When I looked at the data in your demo, it looks like the long form GMT. Today, we are instead blocking the script from sending the .NET property types of DateTime and instead sending a pre-formatted string of the date. Ran into some serialization issues when posting those same objects with DateTime properties on them.
Are you returning your DateTime properties as strings but formatted in this GMT when you serialize your .NET data objects back to the JavaScript handlers?
Hi,
I have an issue in Firefox where the kendo map cannot be panned. It works fine on the other browsers.
Can someone help me with this issue? Here are the details:
Firefox - 138.0.4
Kendo - 2019.1.115
When there is a second item in a row and both are expanded the value is no longer sliced(filtered?) by the first item. My users are used to this with excel etc and really want this functionality how can I achieve it?
Value sum is correct (sliced) for all rows
where second row is expanded and not correct(sliced?).
Here is a simplified version of my code showing the unwanted behavior
<!DOCTYPE html>
<html lang="en">
<head>
<link href="../content/shared/styles/examples-offline.css" rel="stylesheet">
<link href="../../styles/default-ocean-blue.css" rel="stylesheet">
<script src="https://code.jquery.com/jquery-3.7.0.min.js"></script>
<script src="https://unpkg.com/jszip/dist/jszip.min.js"></script>
<script src="../../js/kendo.all.min.js"></script>
<script src="../content/shared/js/console.js"></script>
</head>
<body>
<div id="container">
<div id="pivotgrid"></div>
<div id="configurator"></div>
<div id="pivotbutton"></div>
</div>
<script>
var dataSource = new kendo.data.PivotDataSourceV2({
"data": [
{ "Value": 77, "ASort": 2, "BSort": "b" },
{ "Value": 28, "ASort": 1, "BSort": "a" },
{ "Value": 63, "ASort": 2, "BSort": "a" },
{ "Value": 42, "ASort": 1, "BSort": "b" }
],
rows: [
{ name: "ASort", expand: true },
{ name: "BSort", expand: true }
],
"schema": {
"model": {
"fields": {
"Value": { "type": "number" },
"ASort": { "type": "number" },
"BSort": { "type": "string" }
}
},
"cube": {
"dimensions": {
"ASort": { "caption": "ASort" },
"BSort": { "caption": "BSort" }
},
"measures": {
"Value sum": {
"field": "Value",
"format": "{0:n}",
"aggregate": "sum"
}
}
}
}
});
$(document).ready(function () {
window.pivotgrid = $("#pivotgrid").kendoPivotGridV2({
height: $(window).height() - 2,
dataSource: dataSource
}).data("kendoPivotGridV2");
$("#configurator").kendoPivotConfiguratorV2({
dataSource: pivotgrid.dataSource,
filterable: true,
sortable: true
});
$("#pivotbutton").kendoPivotConfiguratorButton({
configurator: "configurator"
});
$("#container").kendoPivotContainer({
configuratorPosition: "left"
});
});
</script>
</body>
</html>