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

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

What I fear, if we don't have something which keeps things together (like XML 
in form widgets does) is the entropy. 
It ressembles the typed or not issue in language (I worked with APL for 20 
years, so I know what you can come with with untyped languages)
AS soon as someone convince me things will be tighten together I will agree. I 
don't see people writing pages using only macro, and that's the glue between 
that I fear

> 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
>            Assignee: Jacques Le Roux
>              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