A couple of post back, someone has made an app to do so. Database is out of scope for this library. It can do everything you can do with B4J, it just gives you an extra easy-to-use layer for the GUI.
Material Design is a nice way to present your site in a modern format.
Using static objects, (loading images from a file folder, hard coded text, etc) one can create a nice looking page.
No doubt, in 6 months time, Google and related partners will come up with another "new" funky design to replace it... (Material Funk).
Common to all design themes (Material being one of many), is the ability to integrate database hooks. However - very few consider this an important aspect.
It is quite easy to model a web page based on static components (of which all ABMaterial examples are built from), but quite another matter when driven from database records.
Most (if not all)
real world sites have a
DB which drives the content. These sites are not blogs that post new content based on some contributors submission (a simple paragraph).
These sites are dynamic - constantly adding and updating data in many tables of the DB to reflect the app scope.
To dismiss "
Database is out of scope" is to state that using this for a real world apps will be difficult for the newcomer.
Currently, this is true.... It need not be.
How can this be resolved? Start with the basics. A knowledge base of examples showing users how to accomplish certain DB tasks in ABMaterial.
Populating tables (relatively easy).
Setting check boxes and radio options (based on DB table values).
Populating combo boxes (and setting current value)
Populating lists
Retrieving (key) values and updating the DB table for each.
As one may infer, I (for one) am frustrated with the learning curve to get this framework working to my expectations.
It is still in beta, looking quite promising as a B4J addition, but lacks the docs (and code) to make it work real world.
I do hope in one months time - I shall EAT all words stated above.
Thanks