Sign in Join
Wiki copytemporary

GUI design: what changed

Revision 0 to 1. Removed lines have a minus sign; added lines have a plus sign.

Title: GUI design

OldNewLine
1+## Overview
2+
3+When working on lazarus, certain design guidelines need to be taken into consideration. To prevent a diversity of styles and ensure the clarity of dialogs. This article tries to summarize these guidelines to help you designing. There is also a buch of screenshots, artwork and dialog information available.
4+
5+- [[GUI design guidelines]]
6+- [[Screenshots / examples]]
7+- [[Lazarus dialogs information]]
8+- [[Lazarus art work]]
9+
10+## Comments
11+
12+### Cross platform
13+
14+What you need to keep in mind is the cross-platform nature of Lazarus. If you make all the changes you suggest, the text on the buttons won't be visible in most standard GTK+ themes, or there will be other problems. I fully support the idea of some tweaks like this, but it should be tested in Linux, Win32 and even in Mac OS X (you guys are running it in Mac OS X already, right?) before it's committed. -[Tony Maro](http://wiki.lazarus.freepascal.org/index.php/User:Tonymaro)
15+
16+
17+That's the only way to do it ;). I have patches of the different dialogs and I would encourage people to test them and post screenshots here. - Darius
18+
19+### CAFE standard
20+
21+I found these ideas on form designs very interesting. If you can, I would be grateful if you could visit <http://www.nvtech.com.au/ProjCurr/CAFE/CAFE.html> to read about a convention called CAFE; standing for "Common Application Front End".
22+
23+The intention of CAFE is not so much to have attractive forms but to have ones that reduce:
24+
25+- training required for application users,
26+- effort required to input data and navigate around the application, and
27+- the chances of a user accidentally inputting incorrect data.
28+
29+The keypoints of the CAFE standard are that it requires each form to:
30+
31+- have a menu of options displayed (ie, not drop down menus or other hidden features)
32+- be capable of being driven by both keyboard and pointing device with the option selection being done primarily by using numbers typed into the number pad on a conventional keyboard (tests have shown that clerks using the keyboard and number-pad are 60% faster than those that have to take their hands off a keyboard to use a pointing device.)
33+- have a field devoted to "form help" which tells the user the purpose of the form and a field devoted to "field help" which changes as focus moves from field to field on the form. The "field help" informs the user of the purpose of the field and the input into that field which is acceptable.
34+
35+If all contractors wrote their applications to conform with the CAFE standard, not only would it ensure an application that was best for business, but it would also allow many different contractors to participate in software development with all applications having exactly the same look and feel and so giving the perception they all belonged to one coherent applications suite. This would be good for everyone.
36+
37+I hope you find these ideas interesting.
38+
39+Kevin Loughrey
40+
41+CEO Non Volatile Technologies Pty Ltd
42+
43+(NVTech supports and promotes the use of Open Source Software as a means of accelerating societal advancement throughout the world.)
44+
45+## See also
46+
47+- [Lazarus look and feel, 16 Jul 2005](http://www.lazarus.freepascal.org/list_archives/lazarus/msg08842.html) Related discussions on the mailing list
48+
49+---
50+*From the Free Pascal wiki, page "GUI design", as it stood on 2014-08-10 after a change by BigChimp, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).*
51+Category: Artwork
52+Category: GUI
53+Category: Guidelines

Back to history