<div dir="ltr"><br><br><div class="gmail_quote">On Sun, Oct 12, 2008 at 4:11 AM, Eeli Kaikkonen <span dir="ltr"><<a href="mailto:eekaikko@mail.student.oulu.fi">eekaikko@mail.student.oulu.fi</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="Ih2E3d">Greg Hellings wrote:<br>
> Possibly place a button next to the free-entry box that pops up a chooser<br>
> dialog which then goes away when the selection is made? Or when you press<br>
><br>
<br>
</div>It's quite obvious that some kind of popup is needed. But that's not<br>
saying anything new. I need very specific suggestions now which can be<br>
analyzed thoroughly. If you haven't read the wiki page, please do it to<br>
see what I mean. We have to think about the visibility, size, mouse<br>
movement length, amount of mouse clicks, different use cases...<br>
<div class="Ih2E3d"><br>
> it toggles the menu bar between single and triple entry boxes?<br>
><br>
<br>
</div>That could be one way to make choosing between two widgets easier, but<br>
It would clutter the UI. I would rather place it in the View menu or<br>
config dialog, though your suggestion gives a quicker and easier way to<br>
change the widget. And I would still prefer one well-designed widget<br>
over two worse ones.</blockquote><div><br></div></div>I disagree. I think there are two perfectly reasonable mechanisms already presented: the single text box which responds to a keyboard entry both to receive focus and to indicate entry; and a second one, like the submenu pop-ups that you mention in the wiki article. Fundamentally we're trying to reach the same goal: entering the user's destination. However, that's where the similarity ends. In the same way that I don't want one fantastic device to tell me both when my food is done and when my sleeping is done, I don't want one device to enter my destination with a keyboard and with a mouse. The simplicity of the submenu system for mouse users makes is ideal for mouse use - the simplicity of a single text entry box makes it ideal for keyboard users. Any sort of unified hybrid system is going to sacrifice beauty, simplicity, rapidity or some other base functionality. Don't fight it -- use two systems.<br>
<br>A single key press to capture input in the input box, and a single button to bring up the submenu display would be ideal. And placing the option for which to display in the configure panel or view menu seems perfect. My understanding is that users will tend to choose one and stick with it, so having both displayed simultaneously is confusing and unnecessary. I don't think that any single widget, no matter how well designed, will be as good as two well-designed widgets in the present case.<br>
<br>--Greg<br></div>