Mark A. Fuller wrote:
> If you want to give the designer the actual templates (but not require her to install the entire application), you could write a little script that would load each template, set variables and ->output() it to a file. Something like a script to run through some test cases (generate the page with the user logged in, not logged in, with an error message, with a success message, with the "you have mail" indicator set, etc.). This way the designer could change the template and regenerate some HTML (without actually using the entire application).
One idea that did cross my mind is to create a small web application that simply
fills in some default values to the templates. It should also allow any
parameters to be overridden by the query string. Then if the designer is capable
he/she could just play with the url to see what different states look like.
They could also use something like Firefox + Tamper Data to even make it easier.
Might be overkill but if you did it right it could be reuseable for different
projects.
Thank you for your suggestion! For now, I will give the designer a couple of frozen sets of parameters (stored by 'Storable') and a little application to fill the templates.
he problem is that many parameters are LOOPs, so it will be difficult to set them by the query string.
Matías
--
Matías Alejo García | http://www.nits.com.ar
