That's the main reason, why usability guides will enforce to make things as easy as possible for a new user. (Some might say there's no alternative to Wireshark, but I would say such a person may be right, but still is bit arrogant Please note, that if the user gets stuck somewhere, that's the moment where he/she might abandon to use the program and begin searching for alternatives.
The typical newbie will install a program, "play" a while with that program, and if getting in comfort with it read the documentation to get deeper knowledge. Well, that's actually not the way things work.
"The user should read the documentation (help, getting started, …), which describes the way such settings have to be done". On the devlist, I've often heard something like: This will really make it hard to get a start with these features. So if a newbie installs Wireshark, he or she will be presented by a blank page for capture filters, display filters and coloring rules. There are no Example files, no files with default settings and such. The situation so far (and why it should be changed)Ĭurrently, the installers will only install the files which are needed for Wireshark to do its job. Probably we should add a very limited amount of example capture files too. This includes the files for capture filters, display filters and coloring rules. Some examples which are used by the various installers as a newbie's "starter point".
0 kommentar(er)
