I suppose one solution would be to edit the files in the / zend / Tool / Project / Context / Zf library, which seem to provide the contents / structures used for the finished project.
But this does not seem to be the right decision. Further, I already found in my current research that the tool (zf.bat or sh) checks all directories on php inculde_path for "manifest" and "providers", which, in turn, provide functionality for the tool.
In a Zend_Tool article for a developer, one of the Zend developers just explained some things.
Manifestos
can be used to link and βloadβ as many suppliers as possible.
Providers
, , CLI, , "/". () () , :
zf <method-name> <class-name>
, Zend_Tool_Project_Provider_Abstract
, , , , :
\Zend\\Project\Provider\Manifest.php
:
public function getProviders()
{
return array(
new Zend_Tool_Project_Provider_Profile(),
new Zend_Tool_Project_Provider_Project(),
new Zend_Tool_Project_Provider_Controller(),
new Zend_Tool_Project_Provider_Action(),
new Zend_Tool_Project_Provider_View(),
new Zend_Tool_Project_Provider_Module(),
new Zend_Tool_Project_Provider_ProjectProvider()
);
}
, , CLI .
, , , xml, /Zend/Tool/Project/Provider/ _getDefaultProfile().
, :
- , _getDefaultProfile() true false.
, CLI .
!