[
https://issues.apache.org/jira/browse/OFBIZ-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593151#comment-14593151 ]
Gavin Mabie commented on OFBIZ-6516:
------------------------------------
Check widget-style attribute in many *Form.xml/*Menu.xml files - referenced by ModelFormField.java & ModelMenuItem.java and rendered as className by MacroFormRenderer.java. Currently "buttontext" is defined in style.css for all themes.
> Facilitate the use of Icons in Ofbiz by adding descriptive style to the widget-style attribute in forms
> -------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-6516
> URL:
https://issues.apache.org/jira/browse/OFBIZ-6516> Project: OFBiz
> Issue Type: Sub-task
> Components: ALL APPLICATIONS
> Affects Versions: 14.12.01, 12.04.06, 13.07.03, Upcoming Branch
> Environment: Ofbiz Web UI
> Reporter: Gavin Mabie
> Priority: Minor
>
> Icons can be used to great effect to enhance both the user experience and as well as the look-and-feel of an application. In Ofbiz this is facilitated by using meaningful styles name in the widget-style attribute. Examples are "buttontext create", buttontext delete/remove", "buttontext update". That takes care of the basic CRUD actions. The widget-style attribute is used by front-end designers (on the presentation layer) to create their own designs via macro libraries, stylesheets and javascript files. It will be useful for designers if widget-styles are defined in a standard way in widget definitions (*forms.xml, *menu.xml etc). To set this process in motion I propose the following:
> 1. All "buttontext" widget-style attributes should have a meaningful additional class which describes the action linked to the button, i.e create, update, delete, refresh - depending on the action.
> 2. Add missing descriptive classes like "copy, print, view, download, save" etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Locked
