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

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

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

Nicolas Malin (Jira)

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

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

Hans,

Yes we had this discussion (about enhancing widgets) before. Here I try to make my mind on the efforts which should be engaged concerning backend overhaul. Pesonally (and I guess everybody) I'd not like to *uselessly* spend time on it. So I want to be sure we have a *consensus* and it's the *right one* for the 5-10 future years... For 2-3 years now, I see less efforts put in OFBiz. On one hand, this is normal since OFBiz is already mature. But I also wonder if more people are not heading to other directions (eg Moqui) or use OFBiz in other ways. For instance as an underlying tool (eg using Entity and/or Service Engines but not the rest, ie widgets and minilang). So we need a brainstorming on what is happening and where we should go (put our efforts).

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