since GUI is just a representation of code; it really only exists for the user. A computer doesn't need it to process a command. So the biggest drawback is the lag time for carrying out a command and the memory/processor speed to do so. Imagine that in order to think you would have to draw everything first before doing it--- wouldn't that slow you down just a tad?
2006-10-17 17:38:58
·
answer #1
·
answered by E.Nygma 2
·
0⤊
0⤋
Though a GUI allows a number of different controls on the screen, they all have the same tactile feel when making an input. If the input is via a touchscreen then they all feel flat. If the input is via a trackball, then the same roll-and-click motions are used to manipulate any of the controls. With custom controls, a throttle controlling the speed of an aircraft will be physically larger and have a heavier feel than the volume dial for the radio. This communicates the significance of the action to the user. Imagine trying to drive your car with a mouse and screen as the only controls and you will get an idea of how the feeling of control can be lost.
Custom controls can be laid out in positions that fit with the function they perform. If a VCR has an eject button, intuition says to place it beside the slot through which the tape will emerge. If a GUI is the only means of controlling the device, all controls must appear on that display, which means being further from the related hardware. Another disadvantage of the GUI is that space does not generally permit the important controls to be permanently visible. This may not be acceptable if the device is used in a situation where the user may need emergency access to certain controls, or where some monitored information must always be visible.
A related problem is that if only a GUI is used, it will not be possible to have all of the controls visible at all times. This means that the user may have to explore the interface to find some of the functions. Users may not choose to explore the interface, unless they have reason to believe that functions are present that they have not yet discovered. With all of the controls visible they are more likely to ask themselves "What is that for?" or even better, "That dial must control the time delay," if the dial's purpose has been made obvious by its location and labeling.
Many embedded products get the best of both worlds by adding a graphics screen to support peripheral information, while the most important user dialog still takes place using custom controls. This is an attractive option. It allows little-used modes, such as configuration modes, to be implemented using the GUI alone, while normal running utilizes both the GUI and the custom controls. While the user is manipulating the custom controls, information related to the changes may be displayed on the graphics screen. For example, as the flow of water in a pipe is adjusted on a dial, a diagram depicting the tank could show the water level rise and fall as the user turns the dial up and down. Such graphics are particularly useful for novice users who are building up a conceptual model of how the system works.
2006-10-18 00:43:32
·
answer #2
·
answered by midnightlydy 6
·
0⤊
0⤋
It allows people to use Yahoo Answers so that they can get help on there homework.
The main disadvantage is that GUIs take up system resources.
2006-10-18 00:39:50
·
answer #3
·
answered by mysticman44 7
·
0⤊
0⤋
Huge drawback to a user who could only respond to prompts for keys to press, because the keyboard layout can be learned, unlike a Windows desktop layout. It could be very hard to click on a small icon if you could not see it.
2006-10-18 00:38:16
·
answer #4
·
answered by metallhd62 4
·
0⤊
0⤋
Speed and overhead and requirements of the hardware
2006-10-18 00:35:06
·
answer #5
·
answered by fun_in_chicago 3
·
0⤊
0⤋