[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887598#comment-13887598
]
Paul Piper commented on OFBIZ-5040:
-----------------------------------
@jacques, i think both the arguments stated miss the point completely.
The point is to reduce the XML required ultimately, not increase it. People do
not know our custom XML languages, nor is it a proper way to handle the UI.
What people desire is an easy method to create screens and change the html.
Obviously bringing all screens back to a proper html and improving on the
macros is a foundation to both, but in the end we should not invest time into
screen widgets or minilang at all. It only increases the already enormous
amount of hidden knowledge in our project.
This being said, this ticket should still be about bringing all apps that are
available ootb back to using the existing (or slightly improved macros). Then
and only then, can the changes be made that Antil or all the others are
proposing without having to redo all of the work.
> 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)
