[
https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13887579#comment-13887579
]
Jacques Le Roux commented on OFBIZ-5040:
----------------------------------------
Anil,
It seems Ean, Paul and you are aiming almost the same direction. See for
instance OFBIZ-5522 for a discussion with Ean on Websocket, Backbone and Rivets.
So your idea would be to keep form widgets where they are used now. To provide
in parallel JSON services to allow creating a more flexible UI (this is easily
done). Did I get you correctly?
Will you want to get further by replacing the current UI? I guess not? Or maybe
partly, steps by steps?
Anyway for people who don't want to invest massively in rebulding a new UI for
the backend, the widget forms would still be relevant. And for us a basis for
demonstrating OFBiz OOTB, like our demos do. One of the goals of this Jira
issue is to generate consistent HTML source (including CSS and JS), at least
for the bakend. To style it more easily (Boostrap could help indeed).
Also about the better UX, I'm not sure it's only the widgets forms which are a
problem for users. I believe the way the UI is organised plays an important
role in the disappointing experience new users have (once you know how to
navigate in OFBIz it is still, but at a lesser degree). I think the meain
reason is because the UI is built around the data model, rather than smartly
hidding it for a smoother UX. But that's another story and other means to
resolve it...
> 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)
