Page History

...

Jacopo highlighted that he thought the proposed diagrams of the framework re-organisation was a good idea and something that could be done easily that would give benefits. He said that the OFBiz Data Model was very stable and it is only rarely that any changes are needed. The OFBiz OOTB UI on the other hand was like a 'swiss army knife' trying to be everything to everyone which made it not very business user friendly. In some cases it was generic and in others quite specific. A lot of the screens work only for a specific flow so deviating from this can cause problems. There was also a 'mess of things' put together in one screen that perhaps needed to be separated better into a flow.

He thought that it is possible to provide 3 different 'products' from OFBiz;.

• The existing releases as we have now
• an OFBiz Framework + Data Model release for developers to build their own applications and UI;
• The creation of a limited scope component with a nice flow and UI for Business Users (this could just be a hot deploy component that uses OFBiz existing functionality); It could be included as part of OFBiz by default;

Discussion Topic: Migrating Minilang to Groovy

...