MR Marble - Marble ERP and Simple Screens for MR Moqui

The Marble ERP application and the Simple Screens library it is built from, for MR Moqui, in one component named mr-marble that depends on mr-mantle:

• Simple Screens: a library of screens and screen components (forms, sections, transitions) to be included, extended, or generally reused in applications based on MR Moqui and Mantle. They are under screen/SimpleScreens/ (component://mr-marble/screen/SimpleScreens/...), with template/, and My Account (/apps/my). From the Java Moqui component SimpleScreens.
• Marble ERP: a planning and management application for businesses that produce goods and services, and sell to individuals (B2C) and organizations (B2B). Its shell and dashboard are screen/marble.xml and screen/marble/, mounted at /apps/marble (HTML) and /qapps/marble (QVT); most of its screens are mounted from Simple Screens. From the Java Moqui component MarbleERP.

The two were ported in the forks MrSimpleScreens and MrMarbleERP (Groovy and FreeMarker to JavaScript, XSL-FO to HTML print), then merged into this repository with the commit history of both. The renames from the Java names are in the MR Moqui docs/Moqui-Java-Migration.md; the port is recorded in MIGRATION-STATUS.md, and the test commands are in test/README.md. Java FOP is not required.

To make sure this component loads before yours, add a dependency in your component's component.xml file:

<depends-on name="mr-marble"/>

./moq component-get mr-marble
./moq test mr-mantle mr-marble

Moqui Marble ERP is a comprehensive ERP application rather than being focused on goods like POP Commerce ERP or services like HiveMind PM & Admin. Part of the reason for the combination is that goods oriented businesses also have projects and tasks to manage even if they don't sell them, and services oriented businesses also have equipment and supplies to manage even if they don't sell goods.

It is designed around business activities in 3 categories by the primary roles in the system: Internal, Supplier, and Customer. These activities fit into high level business processes such as Procure to Pay (Supplier interactions) and Order to Cash (Customer interactions), and are combined to support a complete end to end flow.