Completed
Last Updated: 07 Oct 2016 12:16 by ADMIN
ANDREW
Created on: 14 Dec 2011 08:47
Category: DropDownList
Type: Feature Request
14
Fast and responsive UI
Fast and responsive UI rather then flaunt and animated. 

I have played for a while with the demo of the components.
What I noticed is that components with popup elements, such as ComboBox, DatePicker, TimePicker, ... have a small but visible delay, which becomes quite annoying with time.

Look at ComboBox demo, it seems there is some delay due to pre-configured animation effects on the control.  In slower browsers (take Firefox 6.0.2) the delay is obvious. 
The support for animation in general is a cool idea, but in most business applications it is not welcome by users who use application on a daily basis. 

Personaly, looking at the demo I am not sure if I can rely on kendoUI if my application designed for "do the job" rather then "enjoy UI".

I think it would be very nice if the demo has settings to disable all animations, to run it at full speed and demonstrate rich AND really responsive UI.
3 comments
ADMIN
Petyo
Posted on: 07 Oct 2016 12:16
Like all temporary solutions, this one turned into a permanent one:

http://stackoverflow.com/questions/23258378/in-the-kendoui-framework-is-there-a-global-way-to-turn-off-animations
Craig
Posted on: 25 May 2012 15:36
I feel like the animation just need to have some simple config settings. Primarily for timing, from "off" to some dev setting. 

In some cases the controls are too fast (splitter) and can confuse the user about what just happened. Animations, if properly used (not just eye candy) can make the application better and guide the user in their task.

Craig
Andrew
Posted on: 16 Feb 2012 05:42
I'm inclined to agree. I find myself looking for options to disable all animations. Good to have them, but they are out of place in business applications. And the Kendo team is constantly touting the speed and... "awesome-ness" of this platform, so let's not inhibit it in any way!

How about implementing click events with onMouseDown rather than onClick?