You've actually given me a really great idea.
First pass we can "projectize" a directory, basically making a
.zfproject.xml file and using the file and directory contexts to "mark"
items.
Then, we can have what you suggested, a way to convert or detect a
specifc abstract context into a proje
Ralph Schindler-2 wrote:
>
> The alternate naming facilities are in place, the only problem is that
> nothing exposes them yet (this is a matter of finding the use case).
> The only use case that myself and Benjamin came up with was to let thing
> work with existing project... which brings me
Hey Ralph,
I was thinking about this issue too, and I think its very easy to implement
in a multi-step procedure. You would combine human- and machine input
to find a module for example:
zf detect project controller-directory /path/to/controllerDir
zf detect project view-directory /path/to/viewd
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 feature
prodigitalson wrote:
# ability to persist alternate namings of things
# ability to scan existing projects (lower priority, and harder to do)
# ability to use alternate config type (moderate complexity, low priority)
Its ironic that the 3 things i want/use most are not complete and have be
> # ability to persist alternate namings of things
> # ability to scan existing projects (lower priority, and harder to do)
> # ability to use alternate config type (moderate complexity, low priority)
>
Its ironic that the 3 things i want/use most are not complete and have been
ranked low in p
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
>
>
Any top-level application resources: like models, should be extremely
flexible. Having said that, if there is anything to target, I would
like to facilitate this style of development:
http://www.slideshare.net/weierophinney/architecting-your-models
The more confusing parts (For most new devel
True, everithing else would be useless, and deleted, since model can be
anything :)
Regards,
Saša Stamenković
On Tue, Dec 15, 2009 at 4:08 PM, Ralph Schindler
wrote:
> This will generate an empty model file, with the appropriate class name, in
> the appropriate location.
>
> so
>
> zf create m
This will generate an empty model file, with the appropriate class name,
in the appropriate location.
so
zf create model FooBar
will create a file
application/models/FooBar.php
with class name
Application_Model_FooBar
The idea here is that out of the box, the models you create will
I'm curious too. Will it be just empty entity like class User {} without
properties etc?
On Tue, Dec 15, 2009 at 5:57 PM, Саша Стаменковић wrote:
> What will zf create model generate?
>
> Regards,
> Saša Stamenković
>
>
>
> On Tue, Dec 15, 2009 at 3:51 PM, Ralph Schindler > wrote:
>
>> Hello all
What will zf create model generate?
Regards,
Saša Stamenković
On Tue, Dec 15, 2009 at 3:51 PM, 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 ch
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
13 matches
Mail list logo
