Template Library Version 1.4.1

[eluser]Colin Williams[/eluser]
@Randy: First off, thanks for the kind words. I think I see where you are going with add_region() but I don't know... I'm not thinking very logically tonight The placement of regions is provided by the master_template, with receives the regions as variables, like a classic view. If you wanted the added region to output above $footer, you would simply shift it "above" footer in the template's markup. I have a feeling we are on different pages... Feel free to discuss it more.

@Too Pixel:

This mean I can overide your library using a MY_Template.php file, right? Out of this point, what are the benefits to have a library as a core class?

Namespacing in this manner should always be followed, and the only namespace I can rely on, given CodeIgniter's set conventions, is prefixing libraries with "CI_". And yes, this has the added effect of being able to override it like a core class. That's one benefit. The other benefit is something I actually noticed when debugging this release. I created a controller called "Template" to add test code to, and you can imagine the problem that caused: Fatal error: Cannot redefine class "Template". That's reason number two.

I think naming custom Libraries "CI_Library" is a general rule you should follow, especially if you intend to share it.

@dexcell:

The bug is:
You can use $data_content variable(in this case $hello) even it wasn’t passed into sidebar view.

This is the nature of CI, it's Views system, and "embedding" Views. Many people actually see it as a feature, not a bug. Don't fear name clashes, because if your 'sidebar' View was explicitly passed a $hello variable, it would in affect override the 'content' View's $hello variable. Again, CI takes care of this, and Template is just a "wrapper" for CI Views.

@AgentPhoenix: Thanks! Working on 1.5/2.0 (depending on how much goes into it) at the moment.