[jira] [Commented] (OFBIZ-5040) Backend widget & application HTML clean-up

["Jacques Le Roux (JIRA)" <ji...@apache.org>]

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

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

Paul,

I changed the title to assert that this is only for backend. It might be obvious, but better to clarify.

Though I'm pretty sure that if we don't systematically use widgets there will be discrepancies, it's also clear that migrating all current backend templates could be overwhelming. So I propose to evaluate the benefit of each approach (widgets vs ftl macros) in each case and to choose the better for the case.

Experience will guide us and while progressing we should try to build guidelines for the choice above.

The 1st guideline is 
* *When possible, widgets shall be preferred*. 

The reasons are many, obvious ones are 
* they have been already well thought out 
* they guarantee *consistency*
* they are stable

> Backend 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)