generated from mwc/project_banjo_app
7c81e13a97
also could be subtracted form the roster. I also did the
first pass through of the view page. I have a list of things
that I know should be included as part of the view, however
I also am not sure how I want to go about showing this
in the example app itself.
I am a little stuck on this. I think that the mre effective way
to do so would be to make a dummy-roster and add students manually
in order to create the rest of the visual demonstration but to leave the
roster function open to upload one's own roster.
I am really enjoying the application of using the terminal to solve a
problem that I choose. Even though it seems like a small one, there is a
lot of investment (on my part) when I am solving my own problem.
It also makes the wins in this project feel bigger somehow? I think that
students would share that buy in!
I have used the visual coding color coded error prompts (the red lettering)
to help work through the visual side of things. The definitions for the app itself
make sense and I feel confident writing those, however the visual side
of things is tougher! As I work through what to print I tend to lose track of the
() and {} and [] and ""... there are just so many! And they go in such
particular places. So, that color coding has been great to identify problems before
they become probleme burried away.
|
||
|---|---|---|
| cookbook/app | ||
| project/app | ||
| .commit_template | ||
| .gitignore | ||
| planning.md | ||
| poetry.lock | ||
| pyproject.toml | ||