[haiku-development] Re: various problems with current developer head
- From: Adrien Destugues <pulkomandy@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 17 Jan 2015 11:53:58 +0100
On Sat, Jan 17, 2015 at 10:55:33AM +0100, Stephan Aßmus wrote:
> Hi,
>
> > Am 17.01.2015 um 09:22 schrieb Adrien Destugues <pulkomandy@xxxxxxxxx>:
> > On Sat, Jan 17, 2015 at 03:17:01PM +1000, Michael Mounteney wrote:
> >>
> >> 5. HaikuPorts isn't obvious. I eventually noticed the 'logged out'
> >> button (why? Presumably because the ports are still a bit alpha?) so
> >> went to create an account. But there was no captcha code visible, so I
> >> couldn't.
> >
> > I think the user interface guidelines aren't followed here.
>
> Huh?
>
> > What looks
> > like a status bar is actually a menu.
>
> You mean the menu entry which is in the main menu bar and just happens to be
> right-aligned? It looks like a status bar?! I thought it was a clever way to
> not waste any space with the login features. I realize menu entries are
> usually not used dynamically like this, except when you think about
> BMenuFields, perhaps. I’ve also had feedback that this interface was a clever
> idea. Has there been more feedback that users don’t get it that I am not
> aware of? Also, I wonder why one even needs to notice the „Logged out“ entry.
> Since when you try to rate a package, it automatically makes you log in. And
> that is the only situation in which you need to be logged in for. So why does
> it even need to be more obvious?
It's labelled with a status message ("logged out" or "logged in as …"),
while it is actually a menu. So the label doesn't hint to the possible
actions.
That doesn't mean it is wrong or that there is a better solution (I
can't think of one at least), but it's nonstandard.
--
Adrien.
Other related posts:
