Improve the gauge component by allowing reference lines to be shown along the scale.

Proposed properties

scale.reference (array of reference objects or single 'reference' object)
scale.reference.value (where between min and max)
scale.reference.width (line thickness)
scale.reference.label (same configuration properties as scale.labels)
scale.reference.line.width (line thickness)
scale.reference.line.length (radial ray length from start)
scale.reference.line.start (radial ray start from origin)

Hi,

In trying to use the Table Wizard in the Editor, I can see an 'Alignment' option which allows me to set the text alignment (<table style="text-align:center;">) - but I don't see an option for the physical placement of the <table> itself within the HTML.

While I know the 'align' property for the <table> object has been deprecated, we can obviously use <table style="float:right"> - but this requires a user to manually edit the HTML the Table Wizard generates after it has been created, which kind of defeats the object of having a wizard.

We are actively trying to minimise the amount of HTML knowledge people need to use these tools, and the Wizard UI is a definite positive step here - can there not be an option added to it to allow this positioning to be selected in the wizard too?

Thanks,

Steve

Dear,

In the filemanager we can use the icon property in the toolbar.

toolbar.items.icon String

Sets icon for the item. The icon should be one of the existing in the Kendo UI theme sprite.

Is it possible to implement this also for the context menu now it uses next property.

contextMenu.items.spriteCssClass String

Specifies the spriteCssClass of the item.

It's easier to make use of the icon class then the spriteCssClass.
Is this a possible feature?

Kind regards,
ITwIT

Dear,

We are trying to make the FileManager compatible with mobile.
Could there be extra configuration so it hides certain properties of widgets?

An example if mobile:

- Hide the text in the Toolbar
- Hide the TreeView
- Optional hide the search bar and details options

Or are there other possibilities on the roadmap?

Kind regards,
ITwIT

Dear Kendo Support Team,

When we use DateRangePicker, we would like to show empty inputs, if the values aren't set. (They're filled with date format placeholder by default.)
Is there any solution to hide the placeholder text?

Regards,
Peter

add delay parameter for the chart tooltips (like showAfter property for the kendo.ui.tooltip) so you're able to configure if you'd like to see a tooltip if you just move the mouse pointer over a chart.
Parameter should be available on all wrappers esp. MVC.

Tooltip for Shapes in Diagram

Implement containers for the Kendo UI Diagram much like Telerik's RadDiagram for WPF and Silverlight.  The containers need to be able to support connections within parent containers (essentially need to be able to create an entire child diagram within each container).  These containers must also be able to be moved as a unit when the user drags and drops the containers around on the screen.

It would be nice if the diagram control could have undo/redo event.

It would love to have an export feature for Diagram which will give the possibilty to make an export to Microsoft Visio.

It should be allowed to extend the Diagram plot area to more than 20000px and/or to calculate the max scroll width based on the Diagram content.

Automatic Layout and Data Source in case of non-TreeView data

In the diagram control automatic layout and data source works just for a tree view. For example in a non tree view data we would have several levels with items that can have multiple parents. In this case I have to create the items in the diagram manually...it would be nice to update this behaviour and to be able to use the diagram with automatic data source and layout also in the case of a non TreeView data.

Expand/Collapse feature on click of the diagram nodes. 
Load data on demand during enpansion of the node.

While the Diagram component is nice it is not explicitly constrained to OrgChart behavior with custom drill-up and built-in drill-down capability like the control for the ASP.NET AJAX suite has and thus trying to implement it as such would consume too much time.  The Diagram component is amazing and certainly has valid use cases but to extend it for use as an OrgChart with all the behaviors that exist in the pure AJAX control would be a pain.

What about adding dynamic scrollbars to the HTML5 Diagram widget?

As developer I'm familiar with the pan and zoom concept, but customers and normal users are expected to see scroll bars to move around a diagram. 
In this demo

http://demos.telerik.com/kendo-ui/html5-diagram-sample-app

you can add objects that fall outside of the main view, but no scroll bars appears.

Here http://kendoui-feedback.telerik.com/forums/127393-telerik-kendo-ui-feedback/suggestions/6552432-html5-diagram-control-allow-scrolling

was posted a similar request, but the scrollbars Kenshin suggested 
are static.

The scrollbars does't readapt if the work area changes. 

If you move objects around, apply a different zoom, add more elements, and so on.

It will be nice to create shapes with rounded borders

Add built-in support for guidelines that will be visible as an infinite grid of lines, with a snap-to capability.

Its good to have minimize and maximize the shapes drawn with kendo diagram as seen in this example
https://gojs.net/latest/samples/IVRtree.html

it will very useful when we are drawing with a huge data. we can clearly see the actual flow as required

It would be nice if, in addition to "polyline" and "cascading", if there were other options for the shape of the diagram connectors.  I would like to see a "spline" option that possibly follows a similar path to the "cascading" square shape, but flows with curves.   Maybe even a configuration object, instead of a string that could define the parameters of the shape.

{ 
type: "spline", 
mode: "bezier", // or "natual" or any other spline algorithm //
maxCurves: 3, // max number of inversion points in the spline //
curveRadius: 100 // size in pixels //
// any additional properties for configuring the curve, like bezier length, instead of curve radius &c. //
}