thx to both of you. then i am on the right track :)
appreciate it
On 13 Jul., 11:39, Jeremy Burns | Class Outfit
wrote:
> A spot on reply. A broad brush to view it is to start from the database and
> create a model/controller/views for each table. That will take you pretty
> near where you wan
A spot on reply. A broad brush to view it is to start from the database and
create a model/controller/views for each table. That will take you pretty near
where you want to go, and then you can start to combine things together.
Jeremy Burns
Class Outfit
jeremybu...@classoutfit.com
http://www.cl
Ok, so the issue here is you're still thinking about your website/app
as a basic procedural script. Which isn't that hard to do, as that is
kind of the life cycle of a standard HTTP request. However, the trick
here is to stop thinking about your website as your basic php
procedural script, and st
hi,
so far i used one controller/model for the whole user management
(login, logout, register, profile etc.).
now I am heading to a different milestone with my website, and the
user is not in focus anymore. so it makes sense to create a new
controller/model, right? but that seems more like a logi
