View Source

<ac:macro ac:name="note"><ac:parameter ac:name="title">Under Construction</ac:parameter><ac:rich-text-body>
<p>This proposal is under construction and is not ready for review.</p></ac:rich-text-body></ac:macro>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{zone-template-instance:ZFDEV:Zend Proposal Zone Template}

{zone-data:component-name}
Zend_Build for MVC
{zone-data}

{zone-data:proposer-list}
[Wil Sinclair|mailto:wil@zend.com]
{zone-data}

{zone-data:revision}
1.1 - 30 November 2007: Inital draft created.
{zone-data}

{zone-data:overview}
This proposal outlines the structure and behavior of build commands and tasks for the MVC components in Zend Framework.
{zone-data}

{zone-data:references}
* [Ruby on Rails|http://www.rubyonrails.org/]
* [Rails Command Line Reference|http://blogs.tech-recipes.com/johnny/rails-quick-reference/]
* [Symfony Generators|http://www.symfony-project.org/book/1_0/14-Generators]
* [CakePHP|http://manual.cakephp.org/chapter/scaffolding]
{zone-data}

{zone-data:requirements}
* *Must* provide the ability to create a basic MVC application with a bootstrap file.
* *Must* provide the ability to create a modular MVC application with a bootstrap file.
* *Must* provide the ability to create custom application structures with specified controller, view, or modules directories from an arbitrary, but correctly assembled project profile.
* *Must* provide the ability to create and delete views and controllers for the application types above.
* *Must* provide the ability to create all necessary views for CRUD operation for a named entity for the application types above.
* *Must* provide the ability to create and delete modules in a modular MVC application for the application types above.

{zone-data}

{zone-data:dependencies}
* Zend_Exception
* Zend_Build
* Zend_Controller
* Zend_View
{zone-data}

{zone-data:operation}
This proposal provides basic Commands, Tasks, and Resources for MVC applications using Zend_Controller and Zend_View.
{zone-data}

{zone-data:milestones}
Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.
* Milestone 1: [design notes will be published here|http://framework.zend.com/wiki/x/sg]
* Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
* Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
* Milestone 4: Unit tests exist, work, and are checked into SVN.
* Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "\[DONE\]", like this:
* Milestone #: \[DONE\] Unit tests ...
{zone-data}

{zone-data:class-list}
* Zend_Magic_Exception
* Zend_Magic (factory class)
* Zend_Magic_MindProbe
* Zend_Magic_MindProbe_Intent
* Zend_Magic_Action
* Zend_Magic_CodeGen
{zone-data}

{zone-data:use-cases}
||UC-01||

... (see good use cases book)
{zone-data}

{zone-data:skeletons}
{code}
class Zend_Magic_Exception extends Zend_Exception {}

class Zend_Magic {
...
{code}
{zone-data}

{zone-template-instance}]]></ac:plain-text-body></ac:macro>