MVVM is still lacking some of the capability that is provided by the standard widgets. For example a tooltip cannot bind it's content property to a function in a viewmodel.
Posted on:01 Aug 2014 12:29
According to the common UserVoice portal settings, when an idea is declined or completed, you automatically receive your votes for it back, Ciel.
Regarding your comments concerning our AngularJS integration story - see my reply in this thread: http://kendoui-feedback.telerik.com/forums/127393-telerik-kendo-ui-feedback/suggestions/6229505-make-angular-integration-documentation-more-promin
Posted on:29 Jul 2014 17:44
May I also have my votes back, since this topic was closed? I would greatly appreciate it.
Posted on:29 Jul 2014 17:39
I can accept the use of angular, but if we're going to be asked to do that, is there a way that the documentation regarding Kendo and Angular together could be a bit more 'upfront'? Right now it is kind of tucked away in the obscure "getting started with.. " section here: http://docs.telerik.com/kendo-ui/getting-started/introduction
If you are truly going to insist on us using angular with kendo, then I think it should be more noticeable. I think an entire section here would be a good start: http://demos.telerik.com/kendo-ui/
Angular is amazing, and the support for it is extremely welcome - but right now it is disparate and spread out. This is exacerbated by the fact that many of the kendo ui blog posts regarding angular integration refer to the older method, before it became official, and while I've seen a few places where you guys have fixed this, it is not clear everywhere.
I would propose putting more links to the angular documentation right there on the demos page, probably under the large "Tools" section, or given its own category even.
Posted on:25 Jul 2014 11:44
Yikes. You should really adopt angular as the recommended, first, and foremost solution, given your MVVM support is half-assed and no one want programatic jquery mess (then again you are targetted "enterprise" LOB apps)
Posted on:25 Jul 2014 11:36
Kendo UI widgets that support value, source, events, visible and enabled bindings are those who utilize our MVVM framework feature. Other attributes are not supported via MVVM bindings, and presently we don't have plans for that.
You can either ponder using Knockout bindings as a substitute, or utilize our newly introduced and officially supported AngularJS directives for this purpose.
Here's a grid demo demonstrating the latter, for reference:
Posted on:05 May 2014 20:16
Specially and specifically TabStrip has quite pathetic MVVM support: visible :(
Posted on:16 Jan 2014 19:03
The data-min and data-max attributes are also not supported on the date picker.
Posted on:28 Oct 2013 18:10
We've had a lot of trouble with Knockout in general and I find it an underwhelming internal code structure too. I'd really like to see the Kendo team step up their game and get MVVM working better, more like AngularJS in some ways.
Posted on:28 Oct 2013 16:04
I've had a lot of success with knockout.js and the knockout-kendo plug-in from the Kendo Labs in lieu of Kendo's implementation of MVVM. I am disappointed to see that the third party plug-in has far more functionality and is more robust than the first-party MVVM offering. I agree with a previous commenter that at this point MVVM seems like an afterthought.
Posted on:04 Sep 2013 10:45
MVVM seems an after thought, I shudder to think of all the nasty jquery horrors involved in programmatic ally wiring up a view which seems to be the advocated way (i.e. all the online examples).
Posted on:27 Aug 2013 15:52
Just found out that the certain data- attributes are not supported for the grid. for example, I cannot bind to data-editable. ugh