Smarty library names
| From: | Bob Silva | Date: | Fri, 19 Jul 2002 15:54:54 +0000 |
| Subject: | Smarty library names | ||
| Groups: | php.smarty.dev | ||
| Request: | Send a blank email to php-smarty-dev+get-210@lists.php.net to get a copy of this message | ||
We are integrating Smarty into our application framework at Bravenet.com.
In our particular setup, all objects are auto-created through a factory method
based on the classname.
$object =& Framework::CreateObject('Classname');
function CreateObject($classname) {
require($classname);
return new $classname;
}
We also have naming guidelines for our class libraries.
Would you consider removing the hardcoded .class.php when loading the
Compiler and Config_File classes and let the FULL name of the file be
configured with var $compiler_class = 'Smarty_Compiler.class.php' and
var $config_class = 'Config_File.class.php'.
This would make for smoother integration when working within large frameworks
with their own set of rules and guidelines. Their would be no BC problems unless
someone has created their own compiler class (unlikely).
Thanks for your time...great product!
Bob Silva
Senior Developer
Bravenet Web Services