Comment 2 for bug 425583

Hi Henning, the mockup looks great.. I'm looking forward to using Balsamiq for my next UI mockup! It will be great to have all the languages listed there on the page.

Here are a few thoughts:

Small detail: what happens if a person doesn't have any preferred languages set? (Replace the whole para with "Set your preferred languages" link? Or otherwise?) Actually, how does setting my preferred languages help me interact with this page? From what I can see, I'm guessing it doesn't but is simply a good place to provide a link to edit them? I wonder whether it could be beneficial to highlight the persons preferred languages somehow in the complete list, rather than listing them separately? I'm not sure as I don't know that there is currently any benefit to listing them here (other than - as above - providing an appropriate place to edit them).

Medium detail: What would happen if a random user comes and clicks on "Add new language"? This seems to be a new option on your mockup that isn't mentioned here on the bug, and seems to conflict (well, conflict is too strong, grate?) with the information above about reading the FAQ if you want to create a new language.

Bigger detail: I'm not sure why we'd want to have the 'Find language' button when all the languages are listed here on the page? On one side, this is just a minor adjustment to say 'Filter languages in Launchpad'/'Filter language' instead (as the page currently seems to re-get with some extra url filtering params). But, it would be excellent if this current behaviour was the graceful-degradation option, and the JS-enabled page removed the button all-together and filtered the displayed languages as you typed? What do you think? It could be done completely client-side as I'm assuming it's just using the language names and codes? And it might be possible to do this by adapting the lazr.js picker a little?