Looking for advice on php patterns
Posted: Mon Feb 20, 2006 12:16 pm
For an application I am building I would like to have some input on the way I could set up the system. What I've done so far is think about the data I will need. From that I have designed the database tables.
I have a general list of things that I would like to be able to do. Of course I could just start coding all the pages I want to have, using a procedural approach and writing a seperate page for each 'action'.
However, I'm sure that on the long run that's not a good idea. Because the app will change and grow in features a lot, it has to be designed in a modular and flexible way.
The system is one in which users can keep track of their training and climbed routes. They should be able to:
- register/make an account
- log in and make/change their profile
- add, edit and delete training they did and routes they climbed.
- also, visitors of the site should be able to view the routes that have been climbed, in several ways
- probably I'll add a feature that people can choose whether or not their info can be viewed by the public or not
- an admin should be able to edit some of the data, like the users.
I hope the general idea is clear. Now, what I would like to ask is: what approach should I take building an application like this? What patterns would fit here?
I know my question is not very specific, and therefore difficult to answer, but even if people can point me to some other good threads here or articles elsewere, I would be helped. For example, these recent threads were very interesting. But as my knowledge on php patterns is quite limited, I'm not sure what to search for. I've read a bit about MVC but maybe there are some other specific patterns I should take a look at?
I have a general list of things that I would like to be able to do. Of course I could just start coding all the pages I want to have, using a procedural approach and writing a seperate page for each 'action'.
However, I'm sure that on the long run that's not a good idea. Because the app will change and grow in features a lot, it has to be designed in a modular and flexible way.
The system is one in which users can keep track of their training and climbed routes. They should be able to:
- register/make an account
- log in and make/change their profile
- add, edit and delete training they did and routes they climbed.
- also, visitors of the site should be able to view the routes that have been climbed, in several ways
- probably I'll add a feature that people can choose whether or not their info can be viewed by the public or not
- an admin should be able to edit some of the data, like the users.
I hope the general idea is clear. Now, what I would like to ask is: what approach should I take building an application like this? What patterns would fit here?
I know my question is not very specific, and therefore difficult to answer, but even if people can point me to some other good threads here or articles elsewere, I would be helped. For example, these recent threads were very interesting. But as my knowledge on php patterns is quite limited, I'm not sure what to search for. I've read a bit about MVC but maybe there are some other specific patterns I should take a look at?