So at this point, you already have a view, and a controller, but aren’t using any models yet. Let’s make a simple model for our controller to call. Again here is our controller code

Class Controller_About extends Controller 
{
	public function action_index()
	{
                $data = array();
		$data['name'] = "CopyPasteCoder";
		$data['age'] = 27;
		//echo "This is my first attempts at MVC architecture.";
		return View::forge('about', $data);
	}

	public function action_water()
	{
		echo "i'm thirsty";
	}

	public function action_supMe($name = '')
	{
		$data = array();
		$data['name'] = $name;
                $data['age'] = 27;
		return View::forge('about', $data);
	}
}

Now go to /fuelphp/fuel/apps/classes/model/ and create about.php then drop this code in there

namespace Model;

class About extends \Model
{
	public static function get_count()
	{
		$count = 56; //Will get this from the DB SOON.
		return $count;
	}
}

At the time of me writing this, i don’t know why we have to use the namespace Model and extend using \Model. I understand that if we are in namespace Model we do the \Model to retrieve the Model class that is outside of our namespace. But why do I have to use namespace Model in the first place. Why can’t i just extend Model, the way controller does? I tried changing the namespaces, but it never seems to work.Update below! But to get data back from the model, let’s just edit our water function above, and get some data back.

	public function action_water()
	{
		$result = Model\About::get_count();
		echo "i'm thirsty $result";
	}

Just like that we got data back from our Model, pretty easy. One thing, we could do is at the top of our controller file is add use \Model\About;. This lets our controller know about the About model, and let’s us reference it like About::get_count();

So we made a call to our model to get back some data;
“big deal, I could have just done it in the Controller”
You could have, but with separate functions and a separate class, it will make things a little cleaner. It separates duties. So the model can get the data, clean it up. The Controller can take the data, analyze it, then decide what to display. Then the controller can send it to a view for consumption. It is much cleaner than all of this happening in one function.
Again can somebody can explain the reason I can’t use other namespaces for Model (if i figure it out i’ll make a post and let erryone know)?

**UPDATE: I went over to the Forums at FuelPHP, and a bright guy by the name of WanWizard explained it all.

Basically its all about filename resolution using the class/namespaces. 
so I could use
class Model_About extends Model {...}
and call it using \Model_About::get() from the controller
or
use namespace Model;
class About extends \Model{...}
and call it using Model\About::get() from the controller
and in both cases it would call /fuel/app/classes/models/about.php

And in my above example if i created a directory /fuel/app/classes/models
i could put my about.php in there. And use namespace Models if i wanted.