Once in a while, I try out a new Version to see, whether performance has improved. and constantly, I find that this is not the case. The best treeshaking technique from Angular is spoilt by KendoUI components because of all the millions of bytes of script code that get downloaded by your components and lead to a desastrous client experience! Optimization would be as simple as a good redesign. I wonder, why this still did not happen over the last year!
hi guys, We are debating between ag-grid for Kendo ui angular 2....what better to use? 1. Does Kendo UI grid supports RTL (Right To Left)? 2.How to implement expandable row In ag grid angular 2 ? 3. How to implement paging In ag grid angular 2
We started using Kendo Grid extensively. We came across below requirement and confirmed with your support team that the feature is currently not available. We think this would really allow users customise their display.
We would be using a common wrapper class across the org.
We will be displaying list of records from the DB, at times, there are columns which contains a JSON, we need to use a custom template to display the JSON. I understand I can go with an if condition in the template html of grid, but, that would lead me to end up having N number of conditions since we do not have a limited such use cases, each such instance would need to be rendered with different template.
The same is the case with row editing as well, for instance, for columns which accepts a description, we want to show a custom popover which would allow the user to specify the data in the way the customer wants (rich text with lot of customisation)
At a high level if we nail down into steps of the behaviour
1) Columns definition will come as a JSON which would also contain a template reference for any of the columns.
To elaborate more, If firstName and lastName are the columns at the DB level but for grid view I want to show them as a single column.
2) The JSON we are constructing will have a type attribute which would indicate me on whether to use a user defined template or regular one.
3) Corresponding data will be a JSON with possible keys required for the template.