BaseApp update: 1.0.0a3 - phpdoc, Xend_Layout, complex ...

Hi Kevin,

Wonderful setup, a little correction to the BaseApp_Loader class:

public function getInstance($configSection = "development")
{
if (null === self::$instance) {
self::$instance = new self($configSection);
}
return self::$instance;
}

Then you can actually set the config section

Thanks for the great efforts you are making.

oh, btw. I have removed the preceding underscore from $_instance, as this was a protected variable and not private... just my naming conventions. But notice this if you copy/paste the code.

Another point for script execution time optimizing is to consider which directory the application mostly will require files from. The include path is currently being set with BaseApp_Loader::configureIncludePath() that sets BASEAPP_BASEDIR as the first search path. Just by changing this to second search path and having the first set to BASEAPP_BASEDIR."library/" significant performance can be gained. Probably, by adding more paths in a measured priority, you'd be able to gain further speed for your application. Personally, I would move this function out of the loader and have the include paths setup in the bootstrap index.php. Just my 2 cents.

Been studying the implemented MVC pattern that excellently allows for other view engines, I found that the default module's ErrorController selects it's view based on presence of view engine classes. This is great, but it struck my mind, if I'd add other view engines then I'd have to add those to the ErrorController (and possibly other places too). So my solution to this would be to add a list of view engines in the Loader ordered by priority and store it in the Zend_Registry for later use, like this:

Code:
---------------------------------------
$availableViewEngines = array(
"Glacier_View_Smarty",
"Zend_View"
);
Zend_Registry::set("availableViewEngines", $availableViewEngines);
---------------------------------------
End Code

Now I can just in any controller iterate the list and call the available view engine, for example in ErrorController::setupException():

Code:
---------------------------------------
$view = null;
$availableViewEngines = Zend_Registry::get("availableViewEngines");
foreach ($availableViewEngines as $viewEngine) {
if (class_exists($viewEngine) && (! $view)) {
$view = new $viewEngine();
}
}
---------------------------------------
End Code

With this solution I can simply add/remove view engines in the Loader, and their presence/absence will be reflected throughout the system.

Hope this is worth something

Oops! Due to my own implementation and playing around I mistakenly published a wrong class name for the Smarty View. The correct name is of course "BaseApp_View_Smarty" and NOT "Glacier_View_Smarty". Sorry for that.

...and a 'break' would probably be in place in the loop when a view is found