Thanks Ean, I'd have expected a more elaborate comment from you. Wrong direction or simply Sunday (comprehensible and recommended) lazyness? Also if possible please keep comments in Jira ;)
Maybe your experience using Rivets and BackboneJ, and why (apart the size) you preferred them above AngularJS which seems "mainstream" now. Maybe because you are favoring json everywhere or like David says too much tag attributes (which makes me think about too much annotations in Java 7-8)? Also what are your thoughts about form widgets? I have never used Bootstrap from scratch myself (nor SASS or less), but I faced them in projects and I must say I have still a lot to learn. What do you think about http://notes.gross.is/post/43508972396/please-stop-using-twitter-bootstrap ? Also unrelated but while at it, has anyone tried to use https://jersey.java.net/ with OFBiz? Jacques On Sunday, January 26, 2014 4:53 PM, e...@brainfood.com wrote > http://getbootstrap.com/ > > ----- "Jacques Le Roux (JIRA)" <j...@apache.org> wrote: > >> [ >> https://issues.apache.org/jira/browse/OFBIZ-5040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel >> ] >> >> Jacques Le Roux reassigned OFBIZ-5040: >> -------------------------------------- >> >> Assignee: Jacques Le Roux >> >>> 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.
