Jurian Sluiman wrote:
It's a better approach to let the errorController handle the error.
1) The code is centralized in one place
2) You can use the errorController's views to display additional
information
+1
-
--
Wil Moore III
Why is Bottom-posting better than Top-posting:
Since routes are matched in reverse order you will want your least priority
routes to be defined first.
In other words, move your default route to the top.
-
--
Wil Moore III
Why is Bottom-posting better than Top-posting:
http://www.caliburn.nl/topposting.html
DO NOT TOP-POST and DO trim
Le 10/02/11 11:00, Wil Moore III a écrit :
Since routes are matched in reverse order you will want your least priority
routes to be defined first.
In other words, move your default route to the top.
-
--
Wil Moore III
Why is Bottom-posting better than Top-posting:
Dear Zend framework users,
Why does the default router (Zend_Controller_Router_Rewrite) use the complete request for some
routes (Hostname) and only its pathinfo for others (Route, Static, Regex)? It is related to the
version number (version 1 routes check against pathinfo).
When the router
While moving some code further towards ZF2, the dojo application resource
uses Zend\View\ViewEngine in the following function:
public static function enableView(View $view)
{
if (false ===
$view-getPluginLoader('helper')-getPaths('Zend\Dojo\View\Helper')) {
Hey Kevin,
The Dojo component will need to be refactored at a later date.
Currently, our MVC Interfaces proposal was approved and we are moving
towards building an MVC implementation over the next months. Once we
know what the C (Controller) and V (View) look like, we'll apply that to
the
