support custom view class files on the app and not only on %SF_SYMFONY_LIB_DIR%/view

Removes validation of the existence of the view class on %SF_SYMFONY_LIB_DIR%/view

This patch can't work with the actual symfony release.

Granted, the patch was only a workaround.

But, does this mean that if I want to provide a custom view class for my app, I'm forced to put the file in %SF_SYMFONY_LIB_DIR%/view ?

I still think it's impractical to mess with symfony files when I want to implement a customization for this app only.

I'm re-opening this... becuase I feel it's important.

a sfSmaryPlugin would be a fantastic addition to symfony (even though I hate smarty, and don't understand why someone would want to use it, but that choice isn't mine to make), and without this it's not possible.

here's a quick patch to atleast allow people to put a view class in apps/$app/lib/view, however I'm not sure why loading this class can't just be left upto the autoload system?

Index: lib/symfony/controller/sfController.class.php
===================================================================
--- lib/symfony/controller/sfController.class.php       (revision 2414)
+++ lib/symfony/controller/sfController.class.php       (working copy)
@@ -473,7 +473,14 @@
       // view class (as configured in module.yml or defined in action)
       $viewName = $this->getContext()->getRequest()->getAttribute($moduleName.'_'.$actionName.'_view_name', sfConfig::get('mod_'.strtolower($moduleName).'_view_class'), 'symfony/action/view');
       $file     = sfConfig::get('sf_symfony_lib_dir').'/view/'.$viewName.'View.class.php';
-      $class    = is_readable($file) ? $viewName.'View' : 'sfPHPView';
+      if (is_readable($file) || is_readable(sfConfig::get('sf_app_lib_dir').'/view/'.$viewName.'View.class.php'))
+      {
+        $class = $viewName.'View';
+      }
+      else
+      {
+        $class = 'sfPHPView';
+      }
     }

     return new $class();