This is a nice, light-weight method of adding using templates. However, we're not likely to use this tool as it does not appear suitable for large-scale development.
This looks very promising, but the IS director is researching this technology.
Apparently, we can use the Mason Component Interpreter directly, but this is likely to have performance issues. We need to address this issue, but we're looking for the most cost-effective solution that fits our current architecture. Therefore, I'm wondering about the following:
- Do any monks have any experience using Mason with IIS?
- What recommendations would you make regarding an HTML templating system with IIS and why do you make said recommendations?
- Ideally, we'd like something that is easy for our graphic designers to work with. They are somewhat resistant to learning anything that they consider "programming." Embedding Perl directly within HTML documents scares the heck out of them. Just showing them HTML::Template tags made them nervous.
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.