Hi Ean,
Thanks for expanding on this. For most functions, I think I'm in agreement. If the user wants to do something but the function is invisible or greyed, it can be frustrating. Sometimes it can be better to leave a function visible, because when the user tries to use it, you can communicate why it is that they can't use the function at the moment. You can also say what they would need to change to gain access to the function.
I think most things can simply be hidden from a user that doesn't have access, but we need to watch this. For things a user might reasonably want to do, we need to consider how we can communicate what's needed to achieve their goal.
Cheers
Paul Foxworthy
Ean Schuessler wrote
I'm not so much suggesting a "beginner" mode as I am suggesting that controls be scoped to the role of the logged in user. It just doesn't make sense to show controls that link to screens that the user does not have access to. A side-effect of this would be that an "order entry" user would have greatly simplified screens.
----- "Paul Foxworthy" wrote:
> Hi Ean,
> I am absolutely 100% in agreement that the user experience is a big barrier
> to entry for OFBiz. I am comfortable with Javascript being part of the
> primary user interface, provided there is architectural provision for
> alternatives.
> I do not think that a limited "beginner" mode is the answer. See the thread
> at
>
http://ofbiz.135035.n4.nabble.com/hiding-functionality-in-ofbiz-td3473417.html
> for some discussion on this.
> Cheers
> Paul Foxworthy
--
Ean Schuessler, CTO
[hidden email]
214-720-0700 x 315
Brainfood, Inc.
http://www.brainfood.com
Locked
