[
https://issues.apache.org/jira/browse/OFBIZ-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Busco updated OFBIZ-2118:
-------------------------------
Attachment: ReducedThemeRedundancy.patch
David,
please find attached a new patch that tryes to reduce code redundancy in the
themes.
Basically a new "page-container" DIV is included in header.ftl and footer.ftl
This is generally usefull to have more control from the CSS on the page layout.
This is needed for bluelight theme and does not hurt the default theme.
Doing this, the bluelight footer.ftl can simply include the default footer.ftl.
For the message.ftl I have already committed a similar change (based on
include).
For the header.ftl it is not so simple becouse I added/changed more content.
A thing that we could discuss is moving the "logout" command from the AppMenu
to the Header. Right now, when the bluelight theme is selected, the logout menu
option is shown in the drop-down menu (that IMO is not fine) and an additional
logout command is shown in the header.
I would add a new menu (i.e. headerMenu) that should contain the logout, help,
visualtheme sel., language sel. and timezone sel.
Later, when we will have a user preferences page, the headerMenu should only
include logout, help, and preferences options.
This menu should be defined in the CommonScreen and rendered in the header.ftl
through a ${render.screen} command.
An additional improvement I am thinking (but this is more general) is to have
dynamic menus working passing a map to the menu widget. I am not really very
clear about this but I think that could let us have a simpler appheader.ftl.
> Drop-down Applications Bar
> --------------------------
>
> Key: OFBIZ-2118
> URL: https://issues.apache.org/jira/browse/OFBIZ-2118
> Project: OFBiz
> Issue Type: New Feature
> Components: ALL COMPONENTS
> Reporter: Bruno Busco
> Assignee: David E. Jones
> Fix For: SVN trunk
>
> Attachments: AppMenuDropDown.patch, AppMenuDropDown.patch,
> AppMenuDropDown.patch, ReducedThemeRedundancy.patch, screenshot1.jpg,
> screenshot2.jpg, screenshot3.jpg, screenshot4.jpg, screenshot5.jpg,
> VisualThemeMessage.patch, vt_bluelight.zip, vt_bluelight.zip
>
>
> Hi all,
> we have discussed several times about a new backoffice layout with drop-down
> menus to have less crowded screens.
> I am experimenting some solutions and I would like to show you what I came to
> in order to discuss about it.
> What you can see in the screenshots attached is based on an new visual-theme
> but also on several changes in the decorators.
> The idea is to have a breadcrumbs that is a drop-down menu also.
> The leftmost Item is always "Home" and when the user hover on it the
> applications menu is shown up.
> Then the user can select an application and the application name is shown in
> the second position of the breadcrumbs.
> If the user hovers on it the selected application menu is shown and the user
> can select an option that is shown in third position on breadcrumbs.
> The idea is to have the breadcrumbs to incorporate both the applications
> menu, the single application menu and the tab bars.
> At the right ent of the same line of the breadcrumbs (in the white background
> region) the actual screen name should be visible.
> I think that this way of navigating offers to the user a complete view of all
> applications as a whole.
> For the moment I only attach screenshots to this jira because I need to clean
> my code to make a presentable patch. I just want to hear if you think this is
> a model that we can go through. If the community agrres on this that I will
> spend more time to clean the code and submit a patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
