Header menu

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Header menu

Bruno Busco
Hi devs,
I would like to take your attention to the fact that when selecting the
bluelight theme we get the "logout" option in the drop down menu (and in
some case like projectmgr even the "help" option) that is not really fine.

I did place a "logout" link in the header of the bluelight theme to be ready
to the removal of the "logout" menu-item from the CommonAppMenu.

I propose to create a new _framework_ CommonHeaderMenu with the following
menu-items:
Preferences, Help, Logout

The Preferences link should take to a _framework_ defined screen that let
the user to select its own preferences like:
VisualTheme, Language, TimeZone, etc.
These links could be removed from the header and we will have it less
cowded. The actual Logout menu-item should be removed from the
CommonAppMenu.

The Help link will always be present in the CommonHeaderMenu and we should
remove the actual help link that we have is some AppMenu. The help link
should be resolved with something to what proposed in*
**OFBIZ-2133<https://issues.apache.org/jira/browse/OFBIZ-2133>
*

What do you think about?*

*-Bruno



*
*
Reply | Threaded
Open this post in threaded view
|

Re: Header menu

Jacques Le Roux
Administrator
+1

Jacques

From: "Bruno Busco" <[hidden email]>

> Hi devs,
> I would like to take your attention to the fact that when selecting the
> bluelight theme we get the "logout" option in the drop down menu (and in
> some case like projectmgr even the "help" option) that is not really fine.
>
> I did place a "logout" link in the header of the bluelight theme to be ready
> to the removal of the "logout" menu-item from the CommonAppMenu.
>
> I propose to create a new _framework_ CommonHeaderMenu with the following
> menu-items:
> Preferences, Help, Logout
>
> The Preferences link should take to a _framework_ defined screen that let
> the user to select its own preferences like:
> VisualTheme, Language, TimeZone, etc.
> These links could be removed from the header and we will have it less
> cowded. The actual Logout menu-item should be removed from the
> CommonAppMenu.
>
> The Help link will always be present in the CommonHeaderMenu and we should
> remove the actual help link that we have is some AppMenu. The help link
> should be resolved with something to what proposed in*
> **OFBIZ-2133<https://issues.apache.org/jira/browse/OFBIZ-2133>
> *
>
> What do you think about?*
>
> *-Bruno
>
>
>
> *
> *
>
Reply | Threaded
Open this post in threaded view
|

Re: Header menu

David E Jones-3
In reply to this post by Bruno Busco

On Jan 26, 2009, at 2:44 PM, Bruno Busco wrote:

> Hi devs,
> I would like to take your attention to the fact that when selecting  
> the
> bluelight theme we get the "logout" option in the drop down menu  
> (and in
> some case like projectmgr even the "help" option) that is not really  
> fine.
>
> I did place a "logout" link in the header of the bluelight theme to  
> be ready
> to the removal of the "logout" menu-item from the CommonAppMenu.

Yes, this is a good point. This particular way of organizing the menus  
makes this issues more clear, but really we should have changed this a  
long time ago when the current user's name was added to the header.  
That seems to make the most sense as a place to put the logout link.

If there is no user logged in we could also change that to say "Not  
Logged In" with a "Login" link next to it.

> I propose to create a new _framework_ CommonHeaderMenu with the  
> following
> menu-items:
> Preferences, Help, Logout
>
> The Preferences link should take to a _framework_ defined screen  
> that let
> the user to select its own preferences like:
> VisualTheme, Language, TimeZone, etc.
> These links could be removed from the header and we will have it less
> cowded. The actual Logout menu-item should be removed from the
> CommonAppMenu.

Yes, these are a bit crowded, so +1 on that too (and I agree it  
belongs in the framework as all of the infrastructure for these things  
is in the framework).

-David