Low code is very popular now, but many product managers still don’t know the logic of this implementation. Let me make a simple analysis.
There are two general ideas for dynamic configuration of list pages:
1. Based on the form, the main table and sub table generate codes and modify them manually
2. Split list page display and data processing based on data model
The first method represents jeeplus, jeecg, etc.
The characteristics of this method are first based on the underlying data model, and then configured to generate 1:1 and 1:n associated forms. The system automatically generates crud code. The developer downloads the code and adds corresponding logic processing before publishing.
Configuration mode:
Configure the underlying library table
Configure the corresponding form based on the underlying library table (1-to-many sub table mode can be set)
The second way represents that the nailing should be overlapped and JVs
The characteristics of this method are configured based on the content to be displayed, and the system automatically realizes the underlying data model
Configuration mode:
First configure the list page (displayed fields)
On the configuration list page
Comparison of implementation methods
Demo of online experience
Jeeplus demo link: http://www.jeeplus.org/
Jeecg (privatization) demo link: http://www.jeecg.com/
Open source address: https://github.com/jeecgboot/…
Should take (SaaS platform) demo link: https://www.aliwork.com/
JVs (privatization) demo link: http://frame.bctools.cn/#/login
Open source address: https://gitee.com/software-mi…
Which way do you think is better? Please describe it in the comment area