Menu
Community /Pin to ProfileBookmark
@NogDogMar 30.2011 — #You can see one implementation of it in action with the CodeIgniter video tutorials .@NogDogMar 30.2011 — #You are writing the query in one separate place both for general re-usability issues, as well as for a compartmentalization of responsibility (both key aspects of OOP in general). Similarly you are outputting HTML only in the view for essentially the same reason, allowing you to completely change the actualy HTML and the site's layout without having to touch the controller or model code. So a controller might call a model which returns a data set that the controller puts into an array, then decides which view to use and includes/requires it, and that view makes use of that array to populate some dynamic part of its output.
If you are creating a 3-4 page site that maybe does 1 or 2 queries per page, maybe it's not a big deal to change any aspect of the site. If that expands to 30-40 pages with dozens of different potential database actions and several different business logic flows, suddenly that compartmentalization becomes extremely useful and prevents a lot of potential headaches in terms of testing, debugging, maintaining, enhancing, and so forth.
Anyway, I don't personally care to deal with a lot of the details of implementing a MVC application, which is why I use CodeIgniter in those cases where I feel it's warranted to take such an approach. @NogDogMar 30.2011 — #Here's a sketchy, buggy, skeletal view on how you *might* approach it:
index.php:
controller.php:
UserModel.php:
view_user.php:
Most people just write their views as HTML pages, maybe using "helper" functions to handle the "boiler plate" stuff common to all pages (or just include files). You could make it a bit more OOP by putting the data used by the view into some sort of object, maybe including some general methods for outputting a selected data set in different formats (table, list, json object, etc.?)@NogDogMar 30.2011 — #If is always "okay" to do whatever works and best supports how you want to develop and maintain your application. Whether there are some OOP purists who will disagree with that or not, I don't know and don't really care much. ?
CodeIgniter, for example, comes with a bunch of "helper" functions that you load as needed -- and some that are loaded be default.@NogDogMar 31.2011 — #If I have not suggested it to you already in another thread, I found Matt Zandstra's book [i]PHP 5 Objects, Patterns, and Practice[/i] to be a big help for me to to get a grip on using object-oriented techniques with PHP. It is something that for most of us you just need to keep working at until you reach that "eureka" moment where things start to click and you really start to get it. ?
Looking for MVC tutorial
Hi there,
I’ve been trying to learn OOP and I get it I think but I really want to understand the MVC way of OOP as it seems to make a lot of sense to use that, but I generally don’t understand how to separate them completely. So I was hoping someone (like nog_dog who seems to know everything i want to) could point me in the direction of something thoroughly explaining MVC and how to plan for this approach in a project.
Thanks much in advance!
Sign in
to post a comment10 Comments(s) ↴
0
@NogDogMar 30.2011 — #You can see one implementation of it in action with the 0
@NogDogMar 30.2011 — #If you are creating a 3-4 page site that maybe does 1 or 2 queries per page, maybe it's not a big deal to change any aspect of the site. If that expands to 30-40 pages with dozens of different potential database actions and several different business logic flows, suddenly that compartmentalization becomes extremely useful and prevents a lot of potential headaches in terms of testing, debugging, maintaining, enhancing, and so forth.
Anyway, I don't personally care to deal with a lot of the details of implementing a MVC application, which is why I use CodeIgniter in those cases where I feel it's warranted to take such an approach.
0
@NogDogMar 30.2011 — #Here's a sketchy, buggy, skeletal view on how you *might* approach it:index.php:
[code=php]
<?php
// leaving out general config/connect stuff, class auto-loader, etc....
$ctrl = new Controller();
?>
[/code]controller.php:
[code=php]
<?php
class Controller
{
public function __construct()
{
if(!empty($_GET['user'])) {
$this->getUserInfo();
}
else {
include 'default_view.php';
}
}
public function getUserInfo()
{
$user = new UserModel();
$data['user'] = $user->getUserArray((int)$_GET['user']);
include 'view_user.php';
}
}
?>
[/code]UserModel.php:
[code=php]
<?php
class UserModel
{
public function getUserArray($userId)
{
// stuff here to query DB for $userId and populate array $data
return $data;
}
}
?>
[/code]view_user.php:
[code=php]
<html>
<head><title>View User: <?php echo $data['user']['name']; ?></title></head>
<body>
<h1>Info for <?php echo $data['user']['name']; ?></h1>
<ul>
<li>Age: <?php echo $data['user']['age']; ?></li>
<!-- and so forth... -->
</ul>
</body></html>
[/code]Most people just write their views as HTML pages, maybe using "helper" functions to handle the "boiler plate" stuff common to all pages (or just include files). You could make it a bit more OOP by putting the data used by the view into some sort of object, maybe including some general methods for outputting a selected data set in different formats (table, list, json object, etc.?)
0
@NogDogMar 30.2011 — #If is always "okay" to do whatever works and best supports how you want to develop and maintain your application. Whether there are some OOP purists who will disagree with that or not, I don't know and don't really care much. ?CodeIgniter, for example, comes with a bunch of "helper" functions that you load as needed -- and some that are loaded be default.
0
@NogDogMar 31.2011 — #If I have not suggested it to you already in another thread, I found Matt Zandstra's book [i]PHP 5 Objects, Patterns, and Practice[/i] to be a big help for me to to get a grip on using object-oriented techniques with PHP. It is something that for most of us you just need to keep working at until you reach that "eureka" moment where things start to click and you really start to get it. ?