http://eclipsesource.com/blogs/2009/08/06/ui-design-why-is-that-button-gray/ Eclipse Equinox OSGi Fri, 03 Feb 2012 14:17:31 +0100 hourly 1 http://wordpress.org/?v=3.1.4 http://eclipsesource.com/blogs/2009/08/06/ui-design-why-is-that-button-gray/comment-page-1/#comment-2563 Pramatr Mon, 10 Aug 2009 07:16:46 +0000 http://eclipsesource.com/blogs/?p=2626#comment-2563 Great point, there have been so many times I've wondered what do I have to actually do to enable this button in an application. Even for the most skilled of users it's not always obvious, so displaying those conditions is a nice idea. Great point, there have been so many times I’ve wondered what do I have to actually do to enable this button in an application. Even for the most skilled of users it’s not always obvious, so displaying those conditions is a nice idea.

]]> http://eclipsesource.com/blogs/2009/08/06/ui-design-why-is-that-button-gray/comment-page-1/#comment-2547 Christian Thu, 06 Aug 2009 19:33:53 +0000 http://eclipsesource.com/blogs/?p=2626#comment-2547 In our ERP application we have done just what you suggest. We have built our own little "Condition" framework, where you can add a lot of custom conditions on controls, that will disable them when the condition is not met, and show a tooltip to inform the users of the reason. The conditions typically listen to the model for the view (using databinding), but security conditions (missing a role) are used a lot as well. Its difficult to decide between hiding and disabling controls, but we generelly go with disabling. For the views that are used by the most novice users we normally hide the controls instead (using the same framework). In our ERP application we have done just what you suggest. We have built our own little “Condition” framework, where you can add a lot of custom conditions on controls, that will disable them when the condition is not met, and show a tooltip to inform the users of the reason. The conditions typically listen to the model for the view (using databinding), but security conditions (missing a role) are used a lot as well. Its difficult to decide between hiding and disabling controls, but we generelly go with disabling. For the views that are used by the most novice users we normally hide the controls instead (using the same framework).

]]>