Regular meeting time: 21:30, April 11, Host: Zhang Yixuan
Time for next regular meeting: 21:30, April 12, Host: Hu Binbin
1. Work report
| personnel | Completed the task yesterday | Tasks to be completed tomorrow |
|---|---|---|
| Qiao Xihua | Learned flutter layout and frame | Design personal center homepage. |
| Zhang Yixuan | Learned flutter layout and frame | Design welcome and login pages. |
| Shan Yanbo | Learned flutter layout and frame | Design results query page. |
| Hu Binbin | Completed the overall design of the ER diagram; initially realized the logged data sheet. | Complete the functions of login and empty classroom inquiry. |
| Li Jiacheng | Complete the overall design of the ER diagram; learn the restful API. | Complete the function of timetable query. |
| Du Bowei | Build a project framework; implement VPN login operations. | Handle any errors that may occur in the VPN login section. Build an overall framework for visiting teaching affairs and curriculum centers. |
| Guo Jun | "Team Task Dismantling" blog writing and publishing; reply to previous blog comments | Organize and upload all previous meeting records to make a meeting catalog. |
Second, the meeting screenshot
3. Difficulties encountered at work
-
Communication of data formats and APIs between front-end, back-end and crawlers.
This work requires the front-end to mention the data requirements first, so the front-end needs to sort out the required data and send it to the back-end in order to advance the work, and the front-end UI development will be carried out after this.
-
Discuss data encryption.
In front-end and back-end interactions, it is currently possible to use plain text transmission, and write encryption before the software is released. The corresponding interfaces need to be reserved for the front and back ends.
The data in the database needs to be stored encrypted.
-
Remember to check the code into GitHub in real time and commit in time. The backend and the crawler should handle conflicts when pulling. The crawler creates a new branch, and the back end is transmitted as Pull Request standard.
-
Client local cache problem.
Deliver the front end to discuss it yourself.
4. Burndown chart
front end:
rear end:
5. Code or document check-in records
