I am new to Kendo UI Mobile. I am familiar with building Kendo UI SPA applications using TypeScript modules. In debug configuration require.js is used to load the modules. In release configuration all modules are compiled into a single minified file. I typically use a bootstrapper module to create the kendo.Router, kendo.Layout, kendo.View and my view model instances. My view models are TypeScript classes that inherit from kendo.data.ObservableObject.

I am curious how I would go about creating a Kendo UI Mobile app using TypeScript modules. From reading the documentation on Kendo UI Mobile it appears the views are hooked of to their view models declaratively using data-model assuming the view model instances are global variables. Is there an imperative way of hooking up the views to their view models inside a TypeScript module so that the view model instances are not required to be global variables?

many thanks,

Remco

myHead.jsp


include.jsp


myJs.js


Run this page  => Uncaught TypeError: Object [object Object] has no method 'kendoWindow'
kendo.all.min.js version : v2013.3.1324

I refferred this troubleshooting, but not solved.
Whats wrong. please help...

Hi 

I am using an editor on my page using MVC helper i.e.

 @(Html.Kendo().EditorFor(u = > ....

How do i make it so that when I open the page the cursor is blinking away in the editor ready for me to type.. At the moment I need to click on the editor to give it focus,.

I am sure there is some clever jQuery I need to be using.

Any help much appreciated

Is it possible to use WEB.API as the datasource when its cross domain and needs an Authorization header set?

I know you can do cross domain with jsonp, but I read in another thread that with jsonp you can't use the beforeSend - setRequestHeader.

var aumData = new kendo.data.DataSource({
                   transport: {
                       read: {
                           url: '<%=Common.GetAppSetting("WebApiBaseUrl") %>Portfolio/Clients/Value',
                           dataType: "jsonp",
                           beforeSend: function (req) {
                               req.setRequestHeader("Authorization", "<%= this.webApiToken %>");
                           }
                       }
                   }
                });

According to

http://docs.telerik.com/kendo-ui/api/web/listview#methods-add

you can read that the method add() is adding an empty item as first item and prepares it for editing.

What I expect from the method name is to be able to add a populated item.
Is the only way of doing that to change the data source?

How can I have a week view that displays a 5 day work week?   I don't want to display the weekends.

We are using Kendo Image Browser to handle selecting and inserting images from our CDN. In one situation, though, we aren't using the editor as the image destination, but rather just a text area. I added a custom "select" event, and it fires, but I can't, for the life of me, get a handle on the image HTML, especially in Firefox. On the returned value, there is a property called sender, and sender at times, has container information that has the correct innerHTML. But probably 5-10 times, it doesn't have that info. I just want the HTML so I can insert it into my text area.

Is there a format/event that I should be using? Is this even possible?

Thanks in advance,
-Josh

Hi,

I have Kendo grid and I want to show a view in it as you see attachment.

But I could not do it? Can you send me a sample project about it?

With Q3 2013 SP1 & SP2, when drawing a bar chart that has both negative and positive values, with the y axis intercepting at 0, the bar chart animation for bars to the left of the y-axis originates at the left hand end of the bar. Previously, the animation originated at the y-axis for bars either side of the axis. Are there any work-arounds to reinstate the previous behaviour?

See this JSBin for a working example:

http://jsbin.com/ubixOluZ/1/edit?html,js,output

I have seen a variety of questions centered around creating custom MVVM widgets on this forum, and have not yet seen a good answer on how exactly to create a custom widget that is MVVM aware.  Mr. Holland did a nice job with a data-source aware widget that also binds to MVVM, but it only covers a datasource aware widget and doesn't extend into other bindings that you might want to support in your own custom widgets.  I wanted to post a series of tips I've discovered with creating custom widgets that are fully MVVM aware and that function in the same manner as the Kendo widgets themselves.

In this first post, I will show how to create widget that uses simple options that are defined either from data-someoption attributes, or within the { someoption: 'myvalue'} javascript declarations.   We'll create a widget that uses markup like:
In order to accomplish this, let's start with the boiler plate code for a simple widget extension.
With the boiler plate code, we can start adding in the functionality we'll need to support this widget within the KendoUI framework.  First, we should create an init function.  Kendo will call init during the creation of the widget.
The init function is the entry point for KendoUI framework to initialize our widget.  We'll need to use this skeleton of a function and add in our DOM elements creation, event bindings to handle events within the widgets, and setup of any settings or options that we need to handle during creation.  The options variable is supplied to us by kendo and contains all of the options that are set as data-option value pairs or passed in via the options attribute in a javascript declaration.  If we had an option in markup such as data-someoption, we could reference it here as options.someoption.  This value could also be passed during javascript initialization as { someoption: 'somevalue' }.  In order for options to be read and available in the options collection, we have to declare them in a property called options within our widget.
By exposing this options collection, now have access to these options in the options collection of our widget.  Options will automatically be set by the framework within our options collection without any action on our part.  Each option that is declared using a data-someoption="somevalue" attribute or in the javascript as an options: { someoption: "myvalue" } that also has a corresponding options: {} declaration in our widget will be available in the options collection in the init method, and the provided value will also automatically be updated within this.options in our widget.

We can show the use of the options with a little bit of simple jQuery to set the source elements value to equal the option's value.
We can see that both the options parameter as well as our widget's options property have been set to the value specified in the markup's data-someoption attribute.  We would also see this value from a javascript options attribute if our widget was declared from code.

This fiddle provides a working example of widget options: http://jsfiddle.net/cn172/EuNLh/

The full source code for a very basic widget with simple options support:

In the next post, I'll cover a basic MVVM binding, the value binding.  We'll see how MVVM sets the value of widgets with a data-bind="value: someViewModelProperty" markup and how to reflect that value on our UI.