Written by tacman1123 the 1 Feb 12 at 23:50.

Both Twig (http://twig.sensiolabs.org/) and Smarty (http://www.smarty.net/) are dedicated template engines in PHP that can be used as the V part of a MVC framework. They're fast and support caching. Both use a decorator design pattern, much more flexible that the traditional set of "includes" that force the designer to add all sorts of "if" statements in a complex environment.

Both Twig (http://twig.sensiolabs.org/) and Smarty (http://www.smarty.net/) are dedicated template engines in PHP that can be used as the V part of a MVC framework. They're fast and support caching. Both use a decorator design pattern, much more flexible that the traditional set of "includes" that force the designer to add all sorts of "if" statements in a complex environment.

Written by filhocf the 2 Feb 12 at 14:58.

In the "Edit text elements", to add more one field for final message, that will filled with a thanks text or explanation about the closing of survey.

Is more a consideration's question that a tecnical's question.

In the "Edit text elements", to add more one field for final message, that will filled with a thanks text or explanation about the closing of survey. Is more a consideration's question that a tecnical's question.

Written by nickheycats the 8 Feb 12 at 00:33.

For instance, if someone needs to override the $publicurl value, it has to be done in the config-defaults.php. When a user creates their config.php, they might have all the information they need to set the $publicurl, yet they cannot set the value in the config.php.

By updating the config-defaults.php to first check if the variable has been set, we can keep the user's version of the variable and set a default if needed.

$publicurl = isset($publicurl) ? $publicurl : "$rooturl";

Of course there are several ways to do this same logic.

With the code above, if a user were to set a value for $publicurl in their config.php, it would not be overwritten by the config-defaults.php. If the user does not set the value manually, the value will still be set to the default value.

For instance, if someone needs to override the $publicurl value, it has to be done in the config-defaults.php. When a user creates their config.php, they might have all the information they need to set the $publicurl, yet they cannot set the value in the config.php. By updating the config-defaults.php to first check if the variable has been set, we can keep the user's version of the variable and set a default if needed. $publicurl = isset($publicurl) ? $publicurl : "$rooturl"; Of course there are several ways to do this same logic. With the code above, if a user were to set a value for $publicurl in their config.php, it would not be overwritten by the config-defaults.php. If the user does not set the value manually, the value will still be set to the default value.

Written by tacman1123 the 5 Feb 12 at 13:06.

When tokens are defined, instead of merely asking "how many", it would need to change to a list format that asked the field names (and types, but that's a different issue!)

When tokens are defined, instead of merely asking "how many", it would need to change to a list format that asked the field names (and types, but that's a different issue!)

Written by Shnoulle the 4 Feb 12 at 13:56.

0 : allways show ( default)
1 : hide in css and show if error ( actual no)
2 : completely remove tip ( even in HTML)

0 : allways show ( default) 1 : hide in css and show if error ( actual no) 2 : completely remove tip ( even in HTML)