Template Library Version 1.4

[eluser]Colin Williams[/eluser]
Right, Milos. Like I said, the whole theming directory idea was already in place at one time and it was just as simple as you envisaged. However, let's assume at some point in the application, a programmer decides to use $this->load->view() instead of one of the available Template methods (and there are often situations where doing this makes sense). The load->view() method knows nothing of the Template theme, so the API breaks down. The programmer would be required to pass the theme directory in each instance he uses load->view().

Code:

$content = $this->load->view($this->template->theme .'view_file', $data, TRUE)

So, it's something I would consider adding back in, so long as the above caveat is made clear.

So by doing it this way, it would allow anyone to easily add/modify content within regions without making is messy.

I'm not sure I follow. Currently, regions have only 4 attributes: content, name, wrapper and attributes.

Wrapper and attributes I haven't found much use for and I don't even really promote the use of them. Content must be an array just because that's the data structure Template works with (but again I'm going to shift that burden from the config file)