Skip to end of metadata
Go to start of metadata

<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[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Build for MVC Component Proposal

Proposed Component Name Zend_Build for MVC
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Build for MVC
Proposers Wil Sinclair
Revision 1.1 - 30 November 2007: Inital draft created. (wiki revision: 4)

Table of Contents

1. Overview

This proposal outlines the structure and behavior of build commands and tasks for the MVC components in Zend Framework.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • 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.

4. Dependencies on Other Framework Components

  • Zend_Exception
  • Zend_Build
  • Zend_Controller
  • Zend_View

5. Theory of Operation

This proposal provides basic Commands, Tasks, and Resources for MVC applications using Zend_Controller and Zend_View.

6. Milestones / Tasks

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
  • 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 ...

7. Class Index

  • Zend_Magic_Exception
  • Zend_Magic (factory class)
  • Zend_Magic_MindProbe
  • Zend_Magic_MindProbe_Intent
  • Zend_Magic_Action
  • Zend_Magic_CodeGen

8. Use Cases

UC-01

... (see good use cases book)

9. Class Skeletons

]]></ac:plain-text-body></ac:macro>

]]></ac:plain-text-body></ac:macro>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jan 30, 2008

    <p>Hi,</p>

    <p>Zend_Build dependends on Zend_Build, actually this isn't a very useful information, you should change this.</p>

    <p>Furthermore you should take care of Zend_Layout, which is in the core right now.</p>

    <p>Best regards<br />
    johnpatcher</p>