We are re-writing a very large application in HTML5 and are using Kendo UI.
We've run into a bit of an issue trying to port programmatic restrictions based on user selection. As an example, we show the user a grid of items... and based on their selection within the grid - various components, entire views, or sub-sets of a view may be enabled or disabled.
The UI toolkit we used previously had an 'enabled' property on all visual elements - widgets, containers, etc. Setting enabled='false' on a widget would turn it grey and would prevent interaction. Setting enabled='false' on a container would cause it and all its children to turn grey and prevented interaction.
Some Kendo UI widgets have an 'enabled' property... but it's inconsistent. We've tried to work around this by tearing-down / re-creating views or crawling through a view and disabling its children; neither of these approaches are practical.
Is this capability something that is on the Kendo UI roadmap? And, in the meantime - do you have any suggestions or best practices that might help?
We've run into a bit of an issue trying to port programmatic restrictions based on user selection. As an example, we show the user a grid of items... and based on their selection within the grid - various components, entire views, or sub-sets of a view may be enabled or disabled.
The UI toolkit we used previously had an 'enabled' property on all visual elements - widgets, containers, etc. Setting enabled='false' on a widget would turn it grey and would prevent interaction. Setting enabled='false' on a container would cause it and all its children to turn grey and prevented interaction.
Some Kendo UI widgets have an 'enabled' property... but it's inconsistent. We've tried to work around this by tearing-down / re-creating views or crawling through a view and disabling its children; neither of these approaches are practical.
Is this capability something that is on the Kendo UI roadmap? And, in the meantime - do you have any suggestions or best practices that might help?