[jira] [Commented] (OFBIZ-5040) Backend widget & application HTML clean-up

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-5040) Backend widget & application HTML clean-up

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882310#comment-13882310 ]

Jacques Le Roux commented on OFBIZ-5040:
----------------------------------------

Paul,

I will answer you on small points later. I just want to add, regarding your last point about *"before introducing html or js based frameworks"* that, as we already discussed, [Ean's and others suggestion about UI|http://tinyurl.com/mbqwgr6] in "UI Boost for Moqui and Apps Based on It" discussion is worth reading...

I'd love to have Ean, Anil, David and other seasonned OFBiz users's opinions on the current topic, and if we should not think twice before engaging any efforts. I have the feeling that OFBiz will not have a second chance to stay in the race in term of modern UI, and we should not waste it. So, with respect to the human ressources which will certainly be engaged in this effort, I wonder if we should not be pragmatic and rather directly look for a more complete and newer solution to our problems...

Of course, we are still at the foundation level of the UI. I want to clarify this also. We all know (at least that's what i think) that the real issue with most of the OFBiz backend is it was never pre-designed but was continuously built around the data model, notably to show all the possibilities. So some parts are a bit clumsy, and are not always easy to grasp when you first use them (once you are used, most is just great, there are plenty of good ideas). That's why Neogia, Opentaps, BigFish and others exist. Anyway, this should not be our concern (here at least), OFBiz is also there to allow improvements above itself.

I wanted that to be clear, we are only discussing about UI fondations here. And more specifically *backend UI*, where all bells and whistles are not needed and would even be counter-productive (think KISS and YAGNI as much as possible).



> 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)