Zend_Tool_Framework Customization

[prodigitalson]

Can anyone elaborate on the .zf.ini properties that are respected or what one needs to do to set up custom profiles?

Ultimately id like to change the project layout a bit. But for now ill settle for enabling certian things. For example these are the key things i want by default in every project:

- Config file format should be XML not INI
- Data dir with log, cache, and uploads
- Public dir with images, js, css

It seems like all this is doable with jsut certain attribs set on the .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to get it to work.

[Ralph Schindler-2]

I am tackling several of these features now, in preparation for the 1.10
release (this code is and will be in the incubator.)

> Can anyone elaborate on the .zf.ini properties that are respected or what one
> needs to do to set up custom profiles?

Custom profiles are pretty much completely, they mostly need
documenting.  Overall, the docs need to be better organized. Currently
if you put a project file in your storage directory at (for example):

.zf/project/profiles/custom.xml

Then with 1.10 zf client, you'll be able to use it like

zf create project -n custom ./directory

This works on my system, but needs to be more throughly tested.

> Ultimately id like to change the project layout a bit. But for now ill
> settle for enabling certian things. For example these are the key things i
> want by default in every project:
>
> - Config file format should be XML not INI
> - Data dir with log, cache, and uploads
> - Public dir with images, js, css
>
> It seems like all this is doable with jsut certain attribs set on the
> .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
> get it to work.

These types of things can definitely be handled by a custom profile.  TO
that though, there are probably a few places where having attributes
persist into the context object make sense (this would make it easier to
customize things like the name of a directory or file).

I'll keep you updated via the mailing list on the new features I'll be
pushing out this week.

-ralph

[beberlei]

Persistent properties for filenames if they deviate from the default filename
would be really awesome. Otherwise its nearly impossible to build a custom
project profile.

Additionally there should be additional basic types like "Directory",
"PhpFile", "OtherFile" which can be used as placeholders for non-application
critical resources that need representation though.

greetings,
Benjamin

On Monday 02 November 2009 04:56:08 pm Ralph Schindler wrote:

> I am tackling several of these features now, in preparation for the 1.10
> release (this code is and will be in the incubator.)
>
> > Can anyone elaborate on the .zf.ini properties that are respected or what
> > one needs to do to set up custom profiles?
>
> Custom profiles are pretty much completely, they mostly need
> documenting.  Overall, the docs need to be better organized. Currently
> if you put a project file in your storage directory at (for example):
>
> .zf/project/profiles/custom.xml
>
> Then with 1.10 zf client, you'll be able to use it like
>
> zf create project -n custom ./directory
>
> This works on my system, but needs to be more throughly tested.
>
> > Ultimately id like to change the project layout a bit. But for now ill
> > settle for enabling certian things. For example these are the key things
> > i want by default in every project:
> >
> > - Config file format should be XML not INI
> > - Data dir with log, cache, and uploads
> > - Public dir with images, js, css
> >
> > It seems like all this is doable with jsut certain attribs set on the
> > .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
> > get it to work.
>
> These types of things can definitely be handled by a custom profile.  TO
> that though, there are probably a few places where having attributes
> persist into the context object make sense (this would make it easier to
> customize things like the name of a directory or file).
>
> I'll keep you updated via the mailing list on the new features I'll be
> pushing out this week.
>
> -ralph

--
Benjamin Eberlei
http://www.beberlei.de

[umpirsky]

Will use this topic to ask sth.

When generating controllers like TwoWordsController if you run zf controller twoWords, view script folder gets name like twoWords instead two-words, similar problem occurs with controller name when running zf controller two-words. 

Is this a bug?

Regards,
Saša Stamenković

On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <[hidden email]> wrote:

I am tackling several of these features now, in preparation for the 1.10 release (this code is and will be in the incubator.)

Can anyone elaborate on the .zf.ini properties that are respected or what one
needs to do to set up custom profiles?

Custom profiles are pretty much completely, they mostly need documenting.  Overall, the docs need to be better organized. Currently if you put a project file in your storage directory at (for example):

.zf/project/profiles/custom.xml

Then with 1.10 zf client, you'll be able to use it like

zf create project -n custom ./directory

This works on my system, but needs to be more throughly tested.

Ultimately id like to change the project layout a bit. But for now ill
settle for enabling certian things. For example these are the key things i
want by default in every project:

- Config file format should be XML not INI
- Data dir with log, cache, and uploads
- Public dir with images, js, css

It seems like all this is doable with jsut certain attribs set on the
.zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
get it to work.

These types of things can definitely be handled by a custom profile.  TO that though, there are probably a few places where having attributes persist into the context object make sense (this would make it easier to customize things like the name of a directory or file).

I'll keep you updated via the mailing list on the new features I'll be pushing out this week.

-ralph

[scss]

I had the same problem. And every time, I had to correct the view
script filename manualy.

There is one more problem (not sure if it is a problem):
When you create a new controller within a module, the class name in
the controller file does not have the module name as the prefix. For
example,
if you create a controller file named "gallery" under module "admin",
the class name is given only as
class GalleryController extends Zend_Controller_Action
whereas it should be
class Admin_GalleryController extends Zend_Controller_Action

As I said not sure if it is a bug/problem but we have to correct the
classname everytime we create a controller under a module.

scs


On Tue, Nov 3, 2009 at 8:55 AM, Саша Стаменковић <[hidden email]> wrote:

> Will use this topic to ask sth.
> When generating controllers like TwoWordsController if you run zf controller
> twoWords, view script folder gets name like twoWords instead two-words,
> similar problem occurs with controller name when running zf controller
> two-words.
> Is this a bug?
>
> Regards,
> Saša Stamenković
>
>
> On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <[hidden email]>
> wrote:
>>
>> I am tackling several of these features now, in preparation for the 1.10
>> release (this code is and will be in the incubator.)
>>
>>> Can anyone elaborate on the .zf.ini properties that are respected or what
>>> one
>>> needs to do to set up custom profiles?
>>
>> Custom profiles are pretty much completely, they mostly need documenting.
>>  Overall, the docs need to be better organized. Currently if you put a
>> project file in your storage directory at (for example):
>>
>> .zf/project/profiles/custom.xml
>>
>> Then with 1.10 zf client, you'll be able to use it like
>>
>> zf create project -n custom ./directory
>>
>> This works on my system, but needs to be more throughly tested.
>>
>>
>>> Ultimately id like to change the project layout a bit. But for now ill
>>> settle for enabling certian things. For example these are the key things
>>> i
>>> want by default in every project:
>>>
>>> - Config file format should be XML not INI
>>> - Data dir with log, cache, and uploads
>>> - Public dir with images, js, css
>>>
>>> It seems like all this is doable with jsut certain attribs set on the
>>> .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
>>> get it to work.
>>
>> These types of things can definitely be handled by a custom profile.  TO
>> that though, there are probably a few places where having attributes persist
>> into the context object make sense (this would make it easier to customize
>> things like the name of a directory or file).
>>
>> I'll keep you updated via the mailing list on the new features I'll be
>> pushing out this week.
>>
>> -ralph
>
>

[umpirsky]

Hehe, better don't use Zend Tool :)

Regards,
Saša Stamenković

On Tue, Nov 3, 2009 at 8:41 AM, scs <[hidden email]> wrote:

I had the same problem. And every time, I had to correct the view
script filename manualy.

There is one more problem (not sure if it is a problem):
When you create a new controller within a module, the class name in
the controller file does not have the module name as the prefix. For
example,
if you create a controller file named "gallery" under module "admin",
the class name is given only as
class GalleryController extends Zend_Controller_Action
whereas it should be
class Admin_GalleryController extends Zend_Controller_Action

As I said not sure if it is a bug/problem but we have to correct the
classname everytime we create a controller under a module.

scs


On Tue, Nov 3, 2009 at 8:55 AM, Саша Стаменковић <[hidden email]> wrote:
> Will use this topic to ask sth.
> When generating controllers like TwoWordsController if you run zf controller
> twoWords, view script folder gets name like twoWords instead two-words,
> similar problem occurs with controller name when running zf controller
> two-words.
> Is this a bug?
>
> Regards,
> Saša Stamenković
>
>
> On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <[hidden email]>
> wrote:
>>
>> I am tackling several of these features now, in preparation for the 1.10
>> release (this code is and will be in the incubator.)
>>
>>> Can anyone elaborate on the .zf.ini properties that are respected or what
>>> one
>>> needs to do to set up custom profiles?
>>
>> Custom profiles are pretty much completely, they mostly need documenting.
>>  Overall, the docs need to be better organized. Currently if you put a
>> project file in your storage directory at (for example):
>>
>> .zf/project/profiles/custom.xml
>>
>> Then with 1.10 zf client, you'll be able to use it like
>>
>> zf create project -n custom ./directory
>>
>> This works on my system, but needs to be more throughly tested.
>>
>>
>>> Ultimately id like to change the project layout a bit. But for now ill
>>> settle for enabling certian things. For example these are the key things
>>> i
>>> want by default in every project:
>>>
>>> - Config file format should be XML not INI
>>> - Data dir with log, cache, and uploads
>>> - Public dir with images, js, css
>>>
>>> It seems like all this is doable with jsut certain attribs set on the
>>> .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
>>> get it to work.
>>
>> These types of things can definitely be handled by a custom profile.  TO
>> that though, there are probably a few places where having attributes persist
>> into the context object make sense (this would make it easier to customize
>> things like the name of a directory or file).
>>
>> I'll keep you updated via the mailing list on the new features I'll be
>> pushing out this week.
>>
>> -ralph
>
>

[Ralph Schindler-2]

>
> Additionally there should be additional basic types like "Directory",
> "PhpFile", "OtherFile" which can be used as placeholders for non-application
> critical resources that need representation though.
>

Directory and File already exist, but they are currently marked as
abstract.  I can change this, and it makes alot of sense.  I will test
these out with a custom profile.

-ralph

[Ralph Schindler-2]

This is fixed in the incubator / code for 1.10

I have a package ready to test under pear.zfcampus.org if you are
willing to try it.

-ralph

scs wrote:

> I had the same problem. And every time, I had to correct the view
> script filename manualy.
>
> There is one more problem (not sure if it is a problem):
> When you create a new controller within a module, the class name in
> the controller file does not have the module name as the prefix. For
> example,
> if you create a controller file named "gallery" under module "admin",
> the class name is given only as
> class GalleryController extends Zend_Controller_Action
> whereas it should be
> class Admin_GalleryController extends Zend_Controller_Action
>
> As I said not sure if it is a bug/problem but we have to correct the
> classname everytime we create a controller under a module.
>
> scs
>
>
> On Tue, Nov 3, 2009 at 8:55 AM, Саша Стаменковић <[hidden email]> wrote:
>> Will use this topic to ask sth.
>> When generating controllers like TwoWordsController if you run zf controller
>> twoWords, view script folder gets name like twoWords instead two-words,
>> similar problem occurs with controller name when running zf controller
>> two-words.
>> Is this a bug?
>>
>> Regards,
>> Saša Stamenković
>>
>>
>> On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <[hidden email]>
>> wrote:
>>> I am tackling several of these features now, in preparation for the 1.10
>>> release (this code is and will be in the incubator.)
>>>
>>>> Can anyone elaborate on the .zf.ini properties that are respected or what
>>>> one
>>>> needs to do to set up custom profiles?
>>> Custom profiles are pretty much completely, they mostly need documenting.
>>>  Overall, the docs need to be better organized. Currently if you put a
>>> project file in your storage directory at (for example):
>>>
>>> .zf/project/profiles/custom.xml
>>>
>>> Then with 1.10 zf client, you'll be able to use it like
>>>
>>> zf create project -n custom ./directory
>>>
>>> This works on my system, but needs to be more throughly tested.
>>>
>>>
>>>> Ultimately id like to change the project layout a bit. But for now ill
>>>> settle for enabling certian things. For example these are the key things
>>>> i
>>>> want by default in every project:
>>>>
>>>> - Config file format should be XML not INI
>>>> - Data dir with log, cache, and uploads
>>>> - Public dir with images, js, css
>>>>
>>>> It seems like all this is doable with jsut certain attribs set on the
>>>> .zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
>>>> get it to work.
>>> These types of things can definitely be handled by a custom profile.  TO
>>> that though, there are probably a few places where having attributes persist
>>> into the context object make sense (this would make it easier to customize
>>> things like the name of a directory or file).
>>>
>>> I'll keep you updated via the mailing list on the new features I'll be
>>> pushing out this week.
>>>
>>> -ralph
>>
>

[umpirsky]

When can we expect 1.10 to be released?

Regards,
Saša Stamenković

On Tue, Nov 3, 2009 at 3:36 PM, Ralph Schindler <[hidden email]> wrote:

This is fixed in the incubator / code for 1.10

I have a package ready to test under pear.zfcampus.org if you are willing to try it.

-ralph

scs wrote:

I had the same problem. And every time, I had to correct the view
script filename manualy.

There is one more problem (not sure if it is a problem):
When you create a new controller within a module, the class name in
the controller file does not have the module name as the prefix. For
example,
if you create a controller file named "gallery" under module "admin",
the class name is given only as
class GalleryController extends Zend_Controller_Action
whereas it should be
class Admin_GalleryController extends Zend_Controller_Action

As I said not sure if it is a bug/problem but we have to correct the
classname everytime we create a controller under a module.

scs


On Tue, Nov 3, 2009 at 8:55 AM, Саша Стаменковић <[hidden email]> wrote:

Will use this topic to ask sth.
When generating controllers like TwoWordsController if you run zf controller
twoWords, view script folder gets name like twoWords instead two-words,
similar problem occurs with controller name when running zf controller
two-words.
Is this a bug?

Regards,
Saša Stamenković


On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <[hidden email]>
wrote:

I am tackling several of these features now, in preparation for the 1.10
release (this code is and will be in the incubator.)

Can anyone elaborate on the .zf.ini properties that are respected or what
one
needs to do to set up custom profiles?

Custom profiles are pretty much completely, they mostly need documenting.
 Overall, the docs need to be better organized. Currently if you put a
project file in your storage directory at (for example):

.zf/project/profiles/custom.xml

Then with 1.10 zf client, you'll be able to use it like

zf create project -n custom ./directory

This works on my system, but needs to be more throughly tested.

Ultimately id like to change the project layout a bit. But for now ill
settle for enabling certian things. For example these are the key things
i
want by default in every project:

- Config file format should be XML not INI
- Data dir with log, cache, and uploads
- Public dir with images, js, css

It seems like all this is doable with jsut certain attribs set on the
.zfproject.xml and pointing to that xml in the .zf.ini but i cant seem to
get it to work.

These types of things can definitely be handled by a custom profile.  TO
that though, there are probably a few places where having attributes persist
into the context object make sense (this would make it easier to customize
things like the name of a directory or file).

I'll keep you updated via the mailing list on the new features I'll be
pushing out this week.

-ralph

[weierophinney]

-- Саша Стаменковић <[hidden email]> wrote
(on Tuesday, 03 November 2009, 03:37 PM +0100):
> When can we expect 1.10 to be released?

We're still trying to determine a date; there are a number of variables
we need to consider. I'm hoping that we can have it before end-of-year.

> On Tue, Nov 3, 2009 at 3:36 PM, Ralph Schindler <[hidden email]>
> wrote:
>
>     This is fixed in the incubator / code for 1.10
>
>     I have a package ready to test under pear.zfcampus.org if you are willing
>     to try it.
>
>     -ralph
>
>
>     scs wrote:
>
>         I had the same problem. And every time, I had to correct the view
>         script filename manualy.
>
>         There is one more problem (not sure if it is a problem):
>         When you create a new controller within a module, the class name in
>         the controller file does not have the module name as the prefix. For
>         example,
>         if you create a controller file named "gallery" under module "admin",
>         the class name is given only as
>         class GalleryController extends Zend_Controller_Action
>         whereas it should be
>         class Admin_GalleryController extends Zend_Controller_Action
>
>         As I said not sure if it is a bug/problem but we have to correct the
>         classname everytime we create a controller under a module.
>
>         scs
>
>
>         On Tue, Nov 3, 2009 at 8:55 AM, Саша Стаменковић <[hidden email]>
>         wrote:
>
>             Will use this topic to ask sth.
>             When generating controllers like TwoWordsController if you run zf
>             controller
>             twoWords, view script folder gets name like twoWords instead
>             two-words,
>             similar problem occurs with controller name when running zf
>             controller
>             two-words.
>             Is this a bug?
>
>             Regards,
>             Saša Stamenković
>
>
>             On Mon, Nov 2, 2009 at 4:56 PM, Ralph Schindler <
>             [hidden email]>
>             wrote:
>
>                 I am tackling several of these features now, in preparation for
>                 the 1.10
>                 release (this code is and will be in the incubator.)
>
>
>                     Can anyone elaborate on the .zf.ini properties that are
>                     respected or what
>                     one
>                     needs to do to set up custom profiles?
>
>                 Custom profiles are pretty much completely, they mostly need
>                 documenting.
>                  Overall, the docs need to be better organized. Currently if
>                 you put a
>                 project file in your storage directory at (for example):
>
>                 .zf/project/profiles/custom.xml
>
>                 Then with 1.10 zf client, you'll be able to use it like
>
>                 zf create project -n custom ./directory
>
>                 This works on my system, but needs to be more throughly tested.
>
>
>
>                     Ultimately id like to change the project layout a bit. But
>                     for now ill
>                     settle for enabling certian things. For example these are
>                     the key things
>                     i
>                     want by default in every project:
>
>                     - Config file format should be XML not INI
>                     - Data dir with log, cache, and uploads
>                     - Public dir with images, js, css
>
>                     It seems like all this is doable with jsut certain attribs
>                     set on the
>                     .zfproject.xml and pointing to that xml in the .zf.ini but
>                     i cant seem to
>                     get it to work.
>
>                 These types of things can definitely be handled by a custom
>                 profile.  TO
>                 that though, there are probably a few places where having
>                 attributes persist
>                 into the context object make sense (this would make it easier
>                 to customize
>                 things like the name of a directory or file).
>
>                 I'll keep you updated via the mailing list on the new features
>                 I'll be
>                 pushing out this week.
>
>                 -ralph
>
>
>
>
>
>

--
Matthew Weier O'Phinney
Project Lead            | [hidden email]
Zend Framework          | http://framework.zend.com/