Chris wrote:
I'm afraid that the GUI is the way forward, while computers can talk
GUIs were a step backwards, and have done nothing but ensure that accessibility issues maximize a loss of productivity for not only those with a11y issues, but the general population.
beginning, a gui can actually do so much more than any CLI, which
For a naive user, a GUI is marginally more productive than a CLI. For a power user, a CLI is about 1000 times more efficient than a GUI. The initial learning curve for a CLI is slightly steeper than a GUI. In either instance,most of that learning curve is nothing more than rote memorization.
but it's not nearly as 'intiuitive as what MS are currently putting out there'.
Microsoft's UI is "intuitive" only because people are familiar with it. [ I don't remember the cites,but there are several journal articles on the unintuitive nature of MS Windows versus the Unix command line with naive users.]
hopefully the User eXperience project at ux.openoffice.org is a good starting point
Their priority should be to make OOo fully a11y compliant. Then add the eye candy that minimizes productivity, and maximizes system resources that accomplish nothing. xan jonathon -- OOo can not correct for incompetence in creating documents from MSO. Furthermore,OOo can not compensate for the defective and flawed security measures used by Microsoft. As such, before using this product for exams that require faulty and defective software, ensure that you will not be unjustly penalized for the incompetence of the organization that requires the use of software that is known to be flawed, defective, bug-ridden, and fails to meet ISO file format standards. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
