It would be great to be able to simply connect the menu widget to a DataSource to populate. It will allow for a data driven menu, instead of having to handle that logic on the client side.
It would be nice if additional template variables where available, the only two: pageNum & totalPages are not enough.
Consider Time of Day & Filename at a minimum.
Would like to suggest 2 features for the spreadsheet which will be very useful
1) Ability to delete specific cell (not just the content, but the cell itself). Currently there is way to delete row or columns, but no cell deletion. When cell is deleted, user should be prompted whether to allow all cells below the deleted cell to shift up, or all cells on the right of it to shift left. Akin to excel
2) Format painter. The ability to "paint" the styles (such as font size, boldness) from existing text to another existing text. Akin to excel.
Support for different calendars (not just Georgian based ones) like Hijri calendars (different types) and so on. To support this you need to have an API overridable calendars to let people define their calendars by themselves.
Every time the user scrolls in a grid with virtual scrolling, the grid asks for the total number of rows satisfying the filtering conditions. This causes the same exact query to be sent to the database multiple times. Instead cache this value and only ask for it if the filters change.
So with normal scrolling down the grid this will generate the following traffic to SQL:
Select Top 100, Skip 0 from Table where...
Select Count(*) from Table where (returns X number of rows)
Select Top 100, Skip 100 from Table where...
Select Count(*) from Table where (returns same X, exact same query)
Select Top 100, Skip 200 from Table where...
Select Count(*) from Table where (returns same X)
and so on
To see this open a copy of the grid with virtual scrolling:
Scroll the grid down:
In Developer Tools observer the result that is sent back to server includes the same:
every time. In terms this will often generate a Select Count(*) being sent to the server in order to supply the answer for the current filters of the grid. An example when a Select count(*) is generated can be seen in your MVC wrappers, for example, where the toDataSourceResult() will cause this same query to repeatedly be sent to the database with every request for new data (use SQL Server Profiler or similiar to see the unnecessary queries). This is also true for your demo implemenations of the server code when used with Kendo UI.
For grids with large data sets, as is often used with virtual scrolling, this can be a slow query.
Instead of asking for the number of rows every time the grid is scrolled, only do so at inatialization and when the filtering conditions are changed (for example use a variable or an event to keep track of the dataSources filters changing).
If the program cannot assume that the same number of rows will be returned, then please implement a setting for developers that we can use to say that the data is not changing.
We look at historical data that are constant and with more than 100k rows, the Select count(*) puts an annecessary strain on the servers.
We could implement caching for this value, but instead the grid should not repetedly ask for the same value multiple times, instead of only when the filters change.
Editor using editable Div container is really better, for various reasons, that editor using iframe.
Inline Editor can be the solution, but I want also a nice standard editor as the standard mode.
A simple and good solution can be add a new parameter as "toolbarContainer" that is a dom element where editor put the toolbar.
If noset in standard mode, editor apply standard strategy and put it in a div on top of iframe.
If noset in inline mode, editor apply standard strategy and put it in a flying popup.
if set, toolbar editor put toolbar in the selected area.
Export to PDF shows the header commands like "Export to PDF", etc. These should be configurable to not be displayed.
Similarly, using a .PdfExport event to hide and show the command columns is functional but should be included as a property to avoid the flashing that the hide/show does to a large element.
Currently we use batch editing in the Grid control. The idea of batch editing is all changes are retained client side until the user presses the save button. When editing a cell a red dirty indicator is placed on the cell. This gives the user an indication that there are unsaved changes. however, when deleting a row, the row just goes away. There is no indication the user must still save. I would like to see rather than the record immediately removed a class applied to the row so we can apply some style like a strikethrough or red background color to indicate a pending delete. Also, we would be able to switch the "delete" button to an "undo" button.
As suggested here : http://www.telerik.com/forums/supporting-both-comma-and-dot-for-decimal-input With this example : http://trykendoui.telerik.com/ikId/2 Having to force either the dot or comma for numerical input is cumbersome in applications where customers input data all day long and it has to be effective. I would suggest a flag named along the lines of "IgnoreCultureOnInput" which would allow you to punch in either the dot or the comma, but have it converted it back into your local for display. Note that the example above is not complete as it is : 1 - locale specific (won't adjust if you locale calls for a comma instead) 2 - does not support text selection
I'm resurrecting this on the suggestion of Todd Anglin. An earlier request for this feature was declined because modern browsers include spell check. However, there are many use cases where this is no use. In my particular case I need: - Spell Check to work in IE8 - Custom (and programmatically accessible) dictionaries - The ability to programmatically turn spell check on/off on a field by field basis
Hi Telerik team.
There is a plan or intention to isolate the Template engine indo a separated file or something?
Introduce an expression builder for specifying filtering the grid by custom rules. Similar to the RadGrid for Silverlight: http://demos.telerik.com/silverlight/#ExpressionEditor/FilteringGridView
The ability to export a grid to excel has been a great addition, we would like the ability to export in CSV and XML also.
It would be very useful to have a disabelDates() method because the suggestion right now is to destroy the calendar and create it again which works but this approach is not acceptable. We need to set different dates based on the current month in the calendar view:
Currently the shared tooltip's position gets in the way of actually seeing the current category's series, as well as hindering any attempts to click on any series behind the tooltip.
Ideally, the tooltip should form off to the side of the current category's visible/clickable elements, either dynamically based on room available, or statically based on configuration (top, bottom, left, right).
In case you need to get the current page now, here are the suggestions made by Progress Technical Support Engineers: