-- gaz1234 <[email protected]> wrote
(on Sunday, 30 September 2012, 09:21 PM -0700):
> I have played around with ZF version 1.11.11 and found the Zend Tool quite
> handy. 
> 
> However I have noticed that in ZF2 there has been a bit of rejigging to Zend
> Framework. I have searched for the zfproject.xml files but can not find it.
> Does this mean that Zend Tool is no longer supported or required?

Correct on both accounts.

Right now, cloning or unpacking the ZendSkeletonApplication and/or
ZendSkeletonModule is the recommended path for creating a project or
module.

Our Console component has been expanded to provide a rich set of
features around tabular data, colorization, interactive prompting, and
more flexible routing than gettext offers. Additionally, it has a number
of hooks into the MVC, which makes it fairly simple to create
Console-based applications.

Eventually, the ZFTool repository will be filled out to provide a larger
featureset of common tasks, such as controller and view script creation,
etc. However, we feel that most of these tasks are relatively easy
compared to actual project and module creation -- which we already have
a solution for.

> My other concern is with Zend Studio 9 (Build id: 20120625) and whether it
> will be compatible with ZF2. 

Studio 10 will have dedicated support for ZF2. In the meantime, you can
add ZF2 as a library to Studio in order to get code hinting support.

> I have downloaded the zf2-tutorial files, used Composer to find the
> dependencies and then created a 'PHP Project from Existing Directory' in
> Zend Studio and I get the following looking file structure with the added
> 'x's. What does this mean? Has anyone else had this problem. I am on a Mac
> 10.6.8.

This I cannot help you with, unfortunately.

-- 
Matthew Weier O'Phinney
Project Lead            | [email protected]
Zend Framework          | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc

-- 
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]


Reply via email to