[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887597#comment-13887597
]
Jacques Le Roux commented on OFBIZ-5040:
----------------------------------------
Quoting myself on dev ML
{quote}
For the common concern about consistent generated HTML source. If we would want
to replace pages currently done with form widgets,
and unleashed Freemarker, this would mean to hide things in macros, right?
I think Adrian's argument about widgets and macros is worth considering
http://markmail.org/message/aysqecll3aolmelz
<<Looking at it another way, with screen widgets you can replace the
existing FreeMarker macros with your own - so the UI can look like anything.
I recently did that for 1Tech Ltd - where I replaced the HTML markup
with Sencha JavaScript.>>
This could be combined with David's suggestion to follow the way Moqui does it
http://markmail.org/message/lohdbc4h2h5jmfil
<<The current implementation in OFBiz parses the XML file into Java classes and
then when rendering generates macro calls to pass the parameters (XML attribute
values, etc) to the FTL macros. A more flexible and extensible approach is to
use the FTL XML processing features directly instead of going through Java
classes. With this approach adding an attribute or support for a whole new
element in the widget XML files is just a matter of adding it to the FTL macros
that process XML elements. >>
{quote}
> 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)
