Author: ts
Date: Tue Feb 19 12:05:56 2008
New Revision: 7409
Log:
- Added "Open issues" section.
Modified:
experimental/MvcTools/design/design.txt
Modified: experimental/MvcTools/design/design.txt
==============================================================================
--- experimental/MvcTools/design/design.txt [iso-8859-1] (original)
+++ experimental/MvcTools/design/design.txt [iso-8859-1] Tue Feb 19 12:05:56
2008
@@ -217,18 +217,37 @@
$router->run();
+Open issues
+===========
+
+Definition of the ezcMvcController interface
+--------------------------------------------
+
+The description and definition of the ezcMvcController interface should be
+reworked. The expected behaviour and API of classes implementing this
+interface should be described in more details.
+
Should the router be selected by a router manager?
--------------------------------------------------
-The router could be selected by a router-manager.
-In that case, some routing mechanism should be in the router manager.
-Router-manager shouldn't be implemented, routers should be factorized instead.
+The router could be selected by a router-manager. In that case, some routing
+mechanism should be in the router manager. Router-manager shouldn't be
+implemented, routers should be factorized instead.
Should the MVC implementation take care of actions/sub-controllers?
-------------------------------------------------------------------
-Controllers have a method looking like : run( ezcMvcInput $input )
-It's up to the controller to figure it's action using $input.
+Controllers have a method looking like : run( ezcMvcInput $input ) It's up to
+the controller to figure it's action using $input.
+
+Shipping of example-implementations
+-----------------------------------
+
+The section `Design overview`_ states that very basic implementations of the
+provided interfaces should be shipped with the component. It must be decided
+if these implementations should be part of the components source code itself
+or should deal as documentation (and therefore reside in the docs/ directory
+instead of src/).
..
--
svn-components mailing list
svn-components@lists.ez.no
http://lists.ez.no/mailman/listinfo/svn-components
