« on: March 02, 2012, 09:57:56 am »
The Smarty system itself is part of the business logic, and probably could be put its own libs directory (I think that is where the example puts it.) The templates that contain the content (foo.tpl) could go in the views folder, or in the Smarty templates dir, whichever works better for you. I think in my implementation I ended up using the Smart templates folder for the templates so I would know they are Smarty templates and not default TinyMVC view files. It really doesn't matter technically, its whatever works for your implementation.
I understand that TinyMVC was build to run as a stand-alone MVC, so there isn't a designated spot for Smarty. However, it seems to me, if one was designed for the other, there would be a clear, concise method of implementation, instructions, defining why, and examples.
Here, I'm being told Smarty is business logic, which tells me it should be part of the Model, except for the templates (I.E. index.tpl, header.tpl, footer.tpl and etc.), which are view elements.
 to add, Smarty basically replaces the TinyMVC views. So instead of $this->load->view() you use $this->smarty->display(). They both load and display a template, but TinyMVC views are just plain PHP files and Smarty views are the Smarty templates.
Here I'm being told Smarty replaces the TinyMVC views.
Realistically, Smarty is all three pieces of the MVC. So, from an organization standpoint and in an effort to sustain some sort of structure, Smarty should be hacked up and put into corresponding directories.
This is what I'm getting at. MVC has no standard. It is a development theory, not a development structure. Software/Web developers are classified into groups, based on their interpretation of MVC. A framework is then built to put structure to each groups interpretation of MVC. Thus, the reason there are so many application frameworks, supposedly based on MVC, for people to choose from (I.E. Struts, Zend, Cake, Tiny and others).
TinyMVC is a MVC application framework for PHP, based on one person's (or a group of people) interpretation of MVC. It is my understanding, the person who built Smarty also built TinyMVC. Yet the idea of how Smarty and TinyMVC should integrate, isn't clear.
As a solution, why not release a TinyMVC download package, which has a working instance of the latest version of Smarty in it? Seeing the two working together is way easier to understand, than references to code, without file names, file names which do not coincide and references to MVC elements without a clearly defined structure.