[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882257#comment-13882257
]
Paul Piper commented on OFBIZ-5040:
-----------------------------------
Yikes, when did the widget part sneak itself in?
Personally, I don't think that widgets are the means customers use to develop
pages. You cannot, nor should you encourage users to use them, since they are
an OFBiz specific implementation with a steep learning curve. Most adopters are
looking for ways to change HTML quickly and widgets are not meant for that.
Though I agree that they have "some" use in the world of backoffice
applications, I would still not go as far as say "When possible, widgets are
preferred".
We want consistency, yes, but freemarker Macros are just as well a solution for
that. When going with macros you have all of the benefits you point out above,
but they are more in line with todays software on the market and hence easier
to understand by new-comers. The only thing missing here is to put more love in
the actual "usefulness" of the macros at hand. So I would propose to rather put
some work into some easy-to-learn macros. If they are easy to use (like
<@ofbiz.widget>Lalalala</@ofbiz.widget>) it is more likely for others to use
them as well.
> 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)
