Hey Jurian,
Zend_Tool is in exactly the state you describe. It's main purpose is
project creation and immediate prototyping. Beyond the basics, there
is/has been too much variation to be able to successfully model all
developers workflows.
1) Not able to use with existing projects (scan files and add to xml)
This is one of those big TODO's. It's not simple as the tool has to be
able to find out the context of every file in a project if possible.
THat means some kind of really smart scanner. It's not impossible to
create, but it is a challenge.
2) Not able to delete objects (and remove from xml)
This is also challenging, but mostly done. While the actions for
delete() are not in the provider, we did add "interactivity support"
some releases ago. This is important b/c if you were to run a delete
command, it should prompt you to ask you if you are sure you want to to
delete it.
3) Not able to configure base classes (e.g. My_Controller_Action instead of
Zend_Controller_Action, same for forms).
This and other "project specific" configurations are also on the TODO.
I'd love to have a Doctrine (esp. for migrations) integration and a deployment
tool. Both were proposed at the wiki (for deployment Zend_Build is proposed)
but they aren't finished. An integrated deployment tool would ease the process
of testing, staging and production environments.
Since Doctrine 2 just went out the door, we'll look into what it will
take to make the doctrine cli work with zf's cli.
Perhaps when ZF2 reaches a stable state, the proposals can be developed
further. I'm willing to support the development of these tools.
Regards, Jurian
