osmocom
/
wireshark
11
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Update the guidelines a bit. 

svn path=/trunk/; revision=53331
This commit is contained in:
Gerald Combs 2013-11-14 23:40:26 +00:00
parent bc17e76462
commit d735fefcf4
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/README.qt
View File

@ -151,9 +151,19 @@ http://www.kdab.com/kdab-products/gammaray/
2. Going forward
DO NOT simply port things over. Every feature, window, and element should be
re-thought. For example, should the user have to navigate two dialogs to get
HTTP request statistics?
DO NOT simply port things over. Much of the GTK+ interface reflects historical
UI conventions and API restrictions which are either no longer relevant or have
been superseded. Every feature, window, and element should be re-thought. When
porting a feature, consider the following:
- Workflow. Excessive navigation and gratuitous dialogs should be avoided or
reduced. For example, the two GTK+ flow graph dialogs have been combined into
one in Qt. Many alert dialogs have been replaced with status bar messages.
- Feedback. Most of the Qt dialogs provide a "hint" area near the bottom which
shows useful information. For example, the "Follow Stream" dialog shows the
packet corresponding to the text under the mouse. The profile management
dialog shows a clickable path to the current profile.
2.1 Coding guidelines