<ac:macro ac:name="info"><ac:parameter ac:name="title">New Proposal Template</ac:parameter><ac:rich-text-body>
<p>This page has been created from a template that uses "zones." To proceed:</p>

<ol>
<li>Edit the page</li>
<li>Replace sample content within each zone-data tag with your own content</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for community review, move this page to the <ac:link><ri:page ri:content-title="Ready for Review" /></ac:link> section on the edit page.</li>
</ol>

<ac:macro ac:name="note"><ac:parameter ac:name="title">No placeholders allowed!</ac:parameter><ac:rich-text-body>
<p>Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.</p></ac:rich-text-body></ac:macro></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_Setup Component Proposal

Table of Contents

1. Overview

Zend_Setup would help developers to create web applications installers. Most web applications needs some initial setup as creating database objects, configuration files or to verify application's license.

2. References

No references here...

3. Component Requirements, Constraints, and Acceptance Criteria

No requirements yet...

4. Dependencies on Other Framework Components

• Zend_Exception
• Zend_Controller
• Zend_Db

5. Theory of Operation

The developer would define a SetupController, that is responsible to call a setup transaction. This transaction would then use Zend_Setup as API for creating databases objects, configuration files and others installation related stuff. Basically, a application setup may be called by http://path/to/app/setup

6. Milestones / Tasks

No milestones yet...

7. Class Index

• Zend_Setup

8. Use Cases

... (see good use cases book)

9. Class Skeletons