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

Jacques Le Roux commented on OFBIZ-5040:
----------------------------------------

I tend to agree Christian (did not check details),

You made another interesting point in OFBIZ-5505, quoting you
{quote}
 think as issues link this occur in FTL files they should be linked to 
OFBIZ-5040 for evaluation for conversion to form widgets. Then new JIRA issues 
could be created due to insufficiencies in form widgets determined by 
conversion evaluation failure and then linked to OFBIZ-5040 as well.
{quote}

> Widget & Application HTML clean-up
> ----------------------------------
>
>                 Key: OFBIZ-5040
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5040
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL APPLICATIONS
>            Reporter: Paul Piper
>              Labels: html, webapp, widget, widgetrendering
>
> I am sure that this is a common thing to know: the current backoffice 
> application relies heavily on widgets. This is good, but the current 
> standard-html-structure is not flexible enough and often lacks proper w3c 
> implementation. 
> To make matters worse, you can often find applications avoiding widgets at 
> all and rather overriding the standards with custom ftl implementations. It 
> is these customizations that break the html on numerous screens and make it 
> difficult, if not tedious to create new themes for the backoffice. 
> This task is hence to:
> * Find a consensus on a new widget standard
> * Go over each of the application ftls and convert these to the new standard 
> * Recreate the themes and simplify/clean-up special rules
> Since redoing the theme is a rather large task, we should consider to add an 
> additional css for now which stylises the replacement html instead of working 
> with the old. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to