Completely Paul for the standardization.
Currently we try to go out all ftl templating from framework to push on
theme with the purpose to have only the screen logic on the framework.
All the rendering would be define and surcharge on the theme.
But standardization on what ?
We have different classification on screen like :
* dedicate screen EventMessages, geoChart, countries
* main decorator screen : GlobalDecorator, LookupDecorator, SimpleDecorator
* embed decorator screen : FindScreenDecorator
My idea like sharing with Julien, Gil and Taher would be to define these
different standard screen as an API you can be use to structure a screen
as guideline.
If the API screen is strong, the theme can rendering it as a like, and
each contributer can create a theme and keep the coherence.
Yes it's a long work but the better way it's start with good base.
Nicolas
Le 28/11/2016 à 21:39, Paul Piper a écrit :
That wasn't meant as trolling, Nicolas. It is a good idea and absolutely
needed. Perhaps as a cautious advice: your problem is going to be
standardization, more so than the UI.
The html in stock ofbiz is a mess and the apps don't really share a common
pattern. For Scipio ERP we cleaned it all up, which took weeks by itself
before we were even able to start on anything useful. Besides that, you will
have to think about the difference in development techniques used. Some apps
rely on *widgets, others on plain ftl. Whatever approach you choose, you
will have to either reimplement all apps, or take care of these differences.
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/DISCUSSION-Improving-the-OFBiz-User-Interface-tp4699708p4699747.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
