Re: Thoughs about naming conflict between model and component

i agree
miles solution is the most appropriate

@Marcelo Andrade
i dont think you

and imagine the array structure - we would have some keys as integer
and some as strings
pretty nasty to work with unless we completely change to the key/value
thing
so not really practicable

On 28 Jan., 08:00, "ecommy.com" <bstdevelopm...@gmail.com> wrote:
> I have not tried it but isn't the Miles idea the best option?  it's
> the simplest and other solutions stated here are just unuseful,
> complicating things when not needed
>
> On 28 ian., 05:08, Marcelo Andrade <mfandr...@gmail.com> wrote:
>
> > On Mon, Jan 25, 2010 at 10:50 AM, Chad Smith <chadsmith...@gmail.com> wrote:
> > > (..)
>
> > I'm not 100% sure and cannot try for now, but doesn't this work?
>
> > <?php
> > class PostsController extends AppController {
> >    var $uses = array('EmailModel'=> 'Email');
> >    var $components = array('EmailComponent'=> 'Email');
> >    var $helpers = array('MyForm'=> 'Form');
> > // ...
>
> > }
>
> > Best regards.
>
> > --
> > MARCELO F ANDRADE
> > Belem, Amazonia, Brazil
>
> > "I took the red pill"

Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.

You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en