Re: new PHPUnit Smarty GUI renderer

Hi, I wrote the Smarty renderer because I need PHPUnit for phpDocumentor, and phpDocumentor already uses Smarty. There are tons of other people using Smarty as well. There's no unnecessary overhead to include the Smarty renderer with PHPUnit (3 really small files). Converting the short tags to Smarty tags took less time than expanding every short tag to an echo or print statement, and if others wish to write a renderer for another template engine, there is nothing stopping them. The way I wrote the smarty renderer requires users to add 1 line of source code to their runtests.php file "include /path/to/Smarty.class.php" So, I see no reason to limit choices when the only reasons against it are philosophical. There is a smarty renderer being written for HTML_QuickForm, perhaps that should be stricken from PEAR for the same reasons? Greg Wolfram Kriesing wrote:

Greg Beaver wrote:

Hi, I don't like setting short_open_tags = on (viewing XML files directly in-browser isn't very fun), so I modified the HTML GUI renderer for PHPUnit to write a new Smarty GUI renderer. It is fully tested, and correctly raises an error if Smarty has not been included. Attached is a .zip containing the extra templates_c directory, Smarty.php and Smarty.tpl files that should be placed in PHPUnit/GUI/ Incidentally, are there any plans to develop a PHPUnit test suite for PHPUnit? It seems like a decent idea :)

sorry i can't resist. But i think replacing the short_tags with the 'long'_tags might be easier and wouldnt require additional files to be loaded. If that is not an opportunity, i think it might make more sense to use a template engine, which is available via PEAR, like IT[X] ... just my 2 cents