[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882287#comment-13882287 ]
Hans Bakker commented on OFBIZ-5040:
------------------------------------
Jacques, i completely agree with you, forms should be used as much as possible, I am talking backend. Frontend macros would be nice.
Forms are much easier to create and maintain, but sure have their limitations. However if there is a limitation, try to add a functions to the widget to solve that.... not sure but did we had this discussion before? I implemented the project manager and had to replace tons of ftl screens in a earlier much more simple version.
Regards,
Hans
> 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)
Locked
