That's good, but I prefer to refer to a more generalised page with other "Examples
of HIGs" http://en.wikipedia.org/wiki/Human_interface_guidelines
Anyone can pick is preferred...
Jacques
Le 28/05/2015 14:58, Paul Mandeltort a écrit :
The OS X UI guidelines doc is a fantastic read. It concisely sums up many
modern Engineering Psychology best practices.
Anyone who is designing front-end or back-end screens should be familiar with
at least the basics.
https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/StartStop.html#//apple_ref/doc/uid/20000957-CH5-SW1 <https://developer.apple.com/library/mac/documentation/UserExperience/Conceptual/OSXHIGuidelines/StartStop.html#//apple_ref/doc/uid/20000957-CH5-SW1>
While there are plenty of OS X-specific guidelines in there, this document is
full of great general guidelines that apply to any software application
regardless of platform. The Menus, UI Design Basics, and Controls and Views
sections are particularly interesting.
—Paul
On May 28, 2015, at 4:40 AM, Jacques Le Roux <[email protected]>
wrote:
Le 27/05/2015 16:41, Paul Mandeltort a écrit :
End user here - online help has always been a weak spot for OFbiz.
I would suggest putting more effort into making things self-documenting whenever
possible. For example, adding descriptive tool tips to what buttons do ("clicking
this will process the order and notify the customer") and more action-oriented names
for things. Apple has great UI guidelines for making these kinds of things self
documenting.
Due to the nature of the projects we (integrators, service providers) support (as eg well
explained Michael) that sounds like a great suggestion to me. Would you have a link to
"Apple has great UI guidelines"?
Thanks
Jacques
--Paul (From Mobile)
On May 27, 2015, at 8:34 AM, Sharan-F <[email protected]> wrote:
Hi All
I'm still looking for some community feedback on this proposal and approach
and now I have a couple of extra questions.
To any OFBiz Service providers out there – how do you manage the online help
when you install or implement OFBiz? (Is it left as it is, do you remove it
or do you create some new online help?)
To the general community at large - what is the overall feeling about
extracting the online help, updating it and then packaging it as a separate
project deliverable that can be easily integrated back into OFBiz?
I'm focussing on the approach first. I think that once we have had the
discussion about that and reach a concensus can we start discussions around
the technology and options to achieve it.
Thanks
Sharan
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/DISCUSSION-OFBiz-Online-Documentation-tp4668869p4669054.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
