pawaitemadisoncollege
commented
2 years ago I like that expand/collapse or hide/show idea @jbrischke. If performance is suffering due to a large amount of data, then yes, making another round trip to the server for info could work. I think it might be worth seeing how performance is and then making a decision.
I think that delete functionality seems better - nice for the user not to have to enter an id number. Looking forward to seeing the redesigned ui in action.
- [ ] Is your time log up to date? Last entry was 10/12? Or should some of those Sept dates actually be Oct dates?
- [ ] is your project plan up to date? There are not any items checked off. Seems to be missing some planning details as well. Think through each user story and when you implement each one.
- [ ] Be sure to use the generic dao so that you don't have a lot of dao copy/paste code. You will still have unit tests for each entity though.
- [ ] I don't think the ERD is showing a relationship between User and Report? Will there be any relationship between User and Game?
- [ ] As you complete the various items identified in these issues, please check them off and then close the issue when everything is complete or otherwise addressed. See marking for a completed item below:
- [x] A completed thing!
jbrischke
@pawaitemadisoncollege
I did what you said about the no ID change to the admin page, I am not 100% sure if I did it the best way though. I want to eventually hide all that input and only have images, those images can be something like a button that when clicked opens up the hidden information or maybe use the selectbyid function to get the data instead of all of it loading hmm.