After the last release when looking at the roadmap for the Q1 2014 release there was mention of a diagramming control.  Now when I look at the roadmap it is not there.  What's going on with the diagramming control?

For the time being the following workaround can be used.

JavaScript:

    <script>
        function pageLoad() {
            var chart = $find("<%=RadHtmlChart1.ClientID%>");
            chart._chartObject.options.categoryAxis.axisCrossingValue = [0, 3];
            chart.repaint();
        }
    </script>
ASPX:

        <telerik:RadHtmlChart ID="RadHtmlChart1" runat="server" Width="600px" Height="400px">
            <PlotArea>
                <Series>
                    <telerik:ColumnSeries AxisName="axis1">
                        <SeriesItems>
                            <telerik:CategorySeriesItem Y="30" />
                            <telerik:CategorySeriesItem Y="20" />
                            <telerik:CategorySeriesItem Y="10" />
                        </SeriesItems>
                    </telerik:ColumnSeries>
                    <telerik:ColumnSeries AxisName="axis2">
                        <SeriesItems>
                            <telerik:CategorySeriesItem Y="3100" />
                            <telerik:CategorySeriesItem Y="2700" />
                            <telerik:CategorySeriesItem Y="1400" />
                        </SeriesItems>
                    </telerik:ColumnSeries>
                </Series>
                <XAxis AxisCrossingValue="2">
                    <Items>
                        <telerik:AxisItem LabelText="item 1" />
                        <telerik:AxisItem LabelText="item 2" />
                        <telerik:AxisItem LabelText="item 3" />
                    </Items>
                </XAxis>
                <YAxis Name="axis1">
                </YAxis>
                <AdditionalYAxes>
                    <telerik:AxisY Name="axis2"></telerik:AxisY>
                </AdditionalYAxes>
            </PlotArea>
        </telerik:RadHtmlChart>

The markup intellisense doesn't work in VS 2008 with Q1 2014.

We would love a couple of Lightswitch HTML controls.  Not expecting the full stack.  

Even if you could just help us understand how to integrate Kendo UI more easily that would help too.  It's a great framework or building fast lightweight apps, but the UI portion is missing many controls and documentation from Telerik, if the controls do integrate.  

ComponentOne seems to have a good handle on it, but we prefer Telerik if we can use it.

None of the demos are displaying correctly.  Take a look at: http://demos.telerik.com/aspnet-ajax/orgchart/examples/overview/defaultcs.aspx.  It appears that the stylesheet might be missing.

There is an on your live demo

http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/rows/detailitemtemplate/defaultcs.aspx

Has telerik ever thought of writing an SSO class or control that would allow someone to add the functionality to sign on to their website using sso and SAML 2.0 for secure login?

I think Telerik missing and OCR control to be complete set. We used Telerik for our web development and recently there was a project that we need to OCR the uploaded document. We would like telerik to be one stop shop for development tools and don't go around to find complimentary controls for OCR. So my suggestion is to add OCR control(s) 

Regards,
Hossein

When RadMenu is present on the page where a RadGrid has to be exported, a JavaScript error is thrown when the response is received. This is observable only in an iframe (or, therefore, a RadWindow).

Different ways to work around this are:

- remove the menu/context menu

- use a regular browser window instead of a RadWindow for this page

- use the ContentTemplate of the RadWindow instead of loading an entire page in it

- try adding the following function override at the end of the content page, just before the closing form tag:
			Telerik.Web.UI.RadMenu.prototype._onMouseOut = function (e)
			{
				var relatedTarget = e.rawEvent.relatedTarget ? e.rawEvent.relatedTarget : e.rawEvent.toElement;

				if (!relatedTarget && !this._isMainElementDescendant(e.target))
				{
					//The mouse is out of the window or the current frame - close the menu
					try
					{
						var that = this;
						setTimeout(
							function ()
							{
								that.close();
							}, this.get_collapseDelay());
					}
					catch (e)
					{
					
					}
				}
			}

If this does not help, try adding this one below:
$telerik.addHandler = function (element, eventName, handler, autoRemove) {
				if (!element._events)
					element._events = {};
			
				var eventCache = element._events[eventName];
				if (!eventCache)
					element._events[eventName] = eventCache = [];
			
				var browserHandler;
				if ($telerik.useAttachEvent(element)) {
					browserHandler = function() {
						var e = {};
						try {
							e = $telerik._getWindow(element).event
						}
						catch (ex) {
						}
						try {
							return handler.call(element, new Sys.UI.DomEvent(e));
						}
						catch (e) {
							
						}
					}
					element.attachEvent('on' + eventName, browserHandler);
				}
				else if (element.addEventListener) {
					browserHandler = function(e) {
						return handler.call(element, new Sys.UI.DomEvent(e));
					}
					element.addEventListener(eventName, browserHandler, false);
				}
			
				eventCache[eventCache.length] = { handler: handler, browserHandler: browserHandler, autoRemove: autoRemove };
				if (autoRemove) {
					var d = element.dispose;
					if (d !== $telerik._disposeHandlers) {
						element.dispose = $telerik._disposeHandlers;
						if (typeof(d) !== "undefined")
							element._chainDispose = d;
					}
				}
			}

Instead of pages like this, which exist for every control and aren't very helpful:
http://www.telerik.com/help/aspnet-ajax/scheduler-appearance-skins.html

I think the skins page should actually render the control and allow developers/designers to select a skin from a drop down to properly demonstrate how the control appears in that skin. 

The logic behind this is somewhat similar to the property explorer pages. As with the property explorer pages, the RenderMode should also be selectable from the proposed skin page because it affects the way the skin is rendered. 

Without this feature I find myself starting a test page, typing in a skin name, save changes, load page, new skin name... repeat, repeat. Please add this feature to make this process a whole lot easier.