| CMakeFiles | ||
| headers | ||
| thirdparty/SQLiteCpp | ||
| .clang-format | ||
| .gitignore | ||
| cmake_install.cmake | ||
| CMakeCache.txt | ||
| CMakeLists.txt | ||
| Customer.cpp | ||
| data.cpp | ||
| Development Guidelines.md | ||
| encrypt.cpp | ||
| graph.png | ||
| Interface.cpp | ||
| main.cpp | ||
| Makefile | ||
| newParkManne.cpp | ||
| oldtest.db3 | ||
| park | ||
| Park_spot.cpp | ||
| Park_time.cpp | ||
| Query.cpp | ||
| readme.md | ||
| test.db3 | ||
use
cmake -G "MinGW Makefiles" -S ./ -B ./build/
mingw32-make
to build the project. it will generate the .exe in /build/park.exe Or click the build icon in vscode shrugs
Parkmanne
A stroll in the park
This is a graph of how everything is connected. If you need to add functionality that doesn't fall in any of these, and you're unsure of what to include, you can decide something like this:
Take my customer class for example. It needs to be able to save to db, so it needs data. It needs to modify and save park_time objects, so it needs those. It needs to encrypt and decrypt passwords. BUT since data already includes encrypt, it doesn't have to be encrypted. So customer includes those.
Another example is Parkspot. It needs information about both customers and save to the database. Since customer also includes data, i don't have to include it again.
Last example:
