I'd be open to ideas on how to scan and determine what the context of a file is.. do you have any ideas? :)

This is next on the list.

-ralph

Jurian Sluiman wrote:
On Tuesday 15 Dec 2009 15:51:53 Ralph Schindler wrote:
Hello all,

As some of you are aware, a significant amount of new features on the
Zend_Tool list for it's release in ZF 1.10.  To get insight into what's
new, please check out:

http://framework.zend.com/issues/browse/ZF-7940

Currently, these features are in trunk and can be installed and used
from trunk.  Keep in mind, there are changes in both bin/ as well as
library/, so you'd need both.

You can also get the latest alpha version of ZF from pear.zfcampus.org
as a PEAR package. http:://pear.zfcampus.org

I am also in the process of cleaning up and restructuring the
documentation for Zend_Tool.

My plan is to get a significant amount of work done in a wiki, get it's
content approved by the users (thats you), then move it into the DocBook
(the manual).  The problem, from my perspective, is that Zend_Tool is
such a large set of features, the current documentation does not
immediately give you the understanding to get started- at least not as
much as I would like.  So please, send me your suggestions here, in IRC
or to my email [ralph dot schindler (a) zend dot com].

http://ralphschindler.com/wiki/index.php/Zend_Tool_Running_Documentation

Some of the more interesting new features:

   Creating a Form:
   zf create form MyForm

   Creating a Model:
   zf create model Foo

   Creating A DbTable (named Bar, for table bar)
   zf create dbtable Bar bar


Thanks for playing & testing it out!
-ralph

What is the status of using Zend_Tool for existing projects? There were questions about it some time ago, but I can't find anything of this in the new features, neither is an issue about this feature in the tracker.

Are there thoughts about it to implement the scanning of a directory to create a configuration file based on existing files / directories? If not, I'll create a new request for this ;)

Regards, Jurian

Reply via email to