[jira] [Comment Edited] (OFBIZ-6689) Have more flexibility in framework and applications regarding theming frameworks.

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

[jira] [Comment Edited] (OFBIZ-6689) Have more flexibility in framework and applications regarding theming frameworks.

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-6689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093615#comment-15093615 ]

Pierre Smits edited comment on OFBIZ-6689 at 1/12/16 9:40 AM:
--------------------------------------------------------------

More flexibilty in how widget style code is handled in the java code and passed on to the *Library.ftl code in themes, enables developers to be able to define more and more modern (responsive) themes.

Current code in the various screen, form, menu and menu-item widget have fixed style definitions, e.g.:
{code}
<form name="ListReports" type="list" separate-columns="true" title="${uiLabelMap.AccountingInvoice} ${uiLabelMap.CommonList}" list-name="invoices" target=""
        odd-row-style="alternate-row" default-table-style="basic-table hover-bar">
{code}
{code}
<menu name="InvoiceSubTabBar" menu-container-style="button-bar button-style-2" default-selected-style="selected">
        <menu-item name="createNew" title="${uiLabelMap.AccountingCreateNewInvoice}" widget-style="buttontext create">
{code}
(in r14.12 branch more than 9.000 defined)

One could say that these are de-facto standards in the back-end applications. And as shown in the dev bootstrap theme, these are corrected with an after page load js function. We can also say that changing the 9.000+ elements is not an option for the short term, to facilitate the requirements of the modern theme frameworks (e.g. Bootstrap and Foundation).

Also dynamically changing the style of a widget element based on variables (e.g. ${widget-style} can't be done at the moment due to the restrictions in the java code.


was (Author: pfm.smits):
More flexibilty in how widget style code is handled in the java code and passed on to the *Library.ftl code in themes, enables developers to be able to define more and more modern (responsive) themes.

Current code in the various screen, form, menu and menu-item widget have fixed style definitions, e.g.:
{code}
<form name="ListReports" type="list" separate-columns="true" title="${uiLabelMap.AccountingInvoice} ${uiLabelMap.CommonList}" list-name="invoices" target=""
        odd-row-style="alternate-row" default-table-style="basic-table hover-bar">
{code}
<menu name="InvoiceSubTabBar" menu-container-style="button-bar button-style-2" default-selected-style="selected">
        <menu-item name="createNew" title="${uiLabelMap.AccountingCreateNewInvoice}" widget-style="buttontext create">
{code}
(in r14.12 branch more than 9.000 defined)

One could say that these are de-facto standards in the back-end applications. And as shown in the dev bootstrap theme, these are corrected with an after page load js function. We can also say that changing the 9.000+ elements is not an option for the short term, to facilitate the requirements of the modern theme frameworks (e.g. Bootstrap and Foundation).

Also dynamically changing the style of a widget element based on variables (e.g. ${widget-style} can't be done at the moment due to the restrictions in the java code.

> Have more flexibility in framework and applications regarding theming frameworks.
> ---------------------------------------------------------------------------------
>
>                 Key: OFBIZ-6689
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6689
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL APPLICATIONS, framework, themes
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Assignee: Pierre Smits
>
> Modern theming frameworks like Bootstrap and Foundation define their own styling elements. In order to facilitate these frameworks (and others), the framework and applications need to be improved.
> This is an umbrella issue to track associated issues and sub tasks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)