OOP Structure for web application
- by Query
Ok so I have a website in which users complete tasks to earn points. When they earn enough points, they rise in rank. The site from my understanding is very basic and only executes one query or two queries at most a page.
There is a user table, a support ticket table, and an orders table.
All of these contain a relational row for username.
Our class was familiarized with OOP back in highschool with Java but that was for video games and I could grasp the concept on why you would need a class player and class enemy.
However I don't understand it's web application. At least not in my situation. I understand the user class might contain stuff like:
getUsername
getPoints
getEmail
setEmail
addPoints (does this belong here? OR only things the user can manipulate should be here?)
etc..
But I'm at a loss with everything else such as user registration.
Can you help give me a wire framework that I could wrap my head around?
Pointing me to a good eBook would help greatly