[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887607#comment-13887607 ]
Jacques Le Roux commented on OFBIZ-5040:
----------------------------------------
You made a point there : <<It increases the already enormous amount of hidden knowledge in our project. >>
BTW it seems we are fighting old battles: typed (XML form widgets) vs untyped (Freemarker), declarative (XML form widgets) vs imperative (Freemarker)
So yes, to be realistic, we should rather focus this Jira on what it's about
# Don't change (keep as is) curent pages done with form widgets
# Improve and create current Freemarker macros
# Use them to clean curent pages done with Freemarker
There are other places to discuss the other points (dev ML and
https://cwiki.apache.org/confluence/display/OFBADMIN/New+Features+Roadmap+-+Living+Document)
> 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)
Locked
