<br><br><div class="gmail_quote">On Sat, Jan 29, 2011 at 2:38 PM, Paul Davis <span dir="ltr"><<a href="mailto:paul@linuxaudiosystems.com">paul@linuxaudiosystems.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Sat, Jan 29, 2011 at 4:41 AM, Nick Copeland<br>
<<a href="mailto:nickycopeland@hotmail.com">nickycopeland@hotmail.com</a>> wrote:<br>
> On the subject of android phones, only a small selection of them and other<br>
> smartphones/tablets actually have keyboards. Surely item #7 for having<br>
> keyboard accelerators for every function is a bit of a misnomer if you are<br>
> talking about State of the Art? This is definitely not a must have.<br>
<br>
</div>alexandre's second list concerned usability, and although its clear<br>
that some platforms do not have or need good keyboard driven<br>
approaches, people are not going to be mixing multitrack audio on<br>
android phones for a while yet. the keyboard is still an incredibly,<br>
incredibly efficient man/machine interface, when it exists.<br>
<br>
i believe that it is/was the lack of such an approach that played an<br>
important role in alex & chris deciding to start OOM, for example,<br>
because they are both aware of the incredible speedup it provides for<br>
professional (read "deeply familiar") users compared to point (with<br>
mouse or finger(s) and click methods.<br>
<div><div></div><br></div></blockquote><div><br>+1<br><br>Touch interfaces, voice (and eventually mind) control - pah! You will have to prise the keyboard and terminal from my cold, dead hands! :D I certainly prefer GUIs that let the user decide if they want to use it primarily or entirely with keyboard or mouse instead of trying to enforce one way or requiring a combo of the two.<br>
<br>Somebody (David?) brought up GUIs that resize well to different display sizes- now that certainly is a worthwhile, non-superficial feature of a modern GUI.<br></div></div>