compared with
Current by Thomas Weidner
on Feb 06, 2011 06:23.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (26)

View Page History
{info:title=New Proposal Template}
This page has been created from a template that uses "zones." To proceed:
<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[{zone-template-instance:ZFPROP:Proposal Zone Template}

# Edit the page
# Replace sample content within each zone-data tag with your own content
# Remove this notice
# Save the page
# When you are ready for community review, move this page to the [Ready for Review] section on the edit page.

{note:title=No placeholders allowed!}
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.

{zone-template-instance:ZFPROP:Proposal Zone Template}

Resource - Requirement Tool

1.0 - 20 December 2009: 01 August 2010: Initial Draft

The "Resource Requirements" tool or RRT is a tool for Zend Framework which checks the actual installation and helps the developer to see if there are missing extensions or ZF components.

* [ZF-7541|]
* [] []

* This component *will* check the actual installation of PHP and the it's extensions.
* This component *will not* do installations or changes in the configuration.
* This component *will* be available for different GUIs (commandline, web, code)


The component is instantiated with a mind-link that ...
The RRT for Zend Framework is a tool which aids the developer or installer of Zend Framework to see which components work with the actual php settings and extensions.
There are multiple modes in which this tool can be used.

1.) command line
Using this tool on command line a user can detect if the framework or single components of the framework are working in the given php installation.
When there are problems the tool will return them and give a hint to see what is necessary.

2.) web
This tool should also be usable in a web-mode. In this mode it will check the installation and return the problems and display them in a nice visual way.

Optionally RRT can also be used to check if possible security configurations are met and return possible problems. For example is register_globals is turned off.

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 1: \[DONE\] Proposal finished
* Milestone 2: Proposal accepted
* Milestone 3: Working implementation
* Milestone 4: Unit tests exist, work, and are checked into SVN.
* Milestone 5: Initial documentation exists. Documentation

If a milestone is already done, begin the description with "\[DONE\]", like this:
* Milestone #: \[DONE\] Unit tests ...
* Milestone 6: Moved to core

* Zend_Magic_Exception
* Zend_Magic (factory class)
* Zend_Magic_MindProbe
* Zend_Magic_MindProbe_Intent
* Zend_Magic_Action
* Zend_Magic_CodeGen
* no classes to use... a single contained tool

See if the whole framework works without problems
>php zf-rrt.php

... (see good use cases book)
Returns a list of components and possible problems
Zend_Version: OK
Zend_XmlRpc: Missing DOMXML extension

See if a single component works without problems
>php zf-rrt.php Zend_Version

Zend_Version: OK


Returns a list of all components like UC1 but with a proper look

class Zend_Magic_Exception extends Zend_Exception {}

class Zend_Magic {
Actually no class skeletons... this is expected to be a single contained tool