this is exactly my point, miles! as they are not triggered manually you need to do some stuff on your own - if the component needs the controller $this object-reference or if the startup() does some important initialization stuff
so for newbies who dont know what they do that sure is not an option some color calculation component though could easily be used in a helper, if it is isolated as described above bottom line: avoid it anyway :) On 1 Aug., 06:10, Shadab Shaikh <rws.sha...@gmail.com> wrote: > I had got your things. > Yes, I know that its bad practice. > > But I am working one kind of application. In which later stage, we will need > to find way by > which we can enter new functionality in the system easliy. We don't need to > touch controller files. We want that if i want to add new functionality than > i can easily do by entering few files/settings with out disturbing earlier > code. > > By above way, if we make genralized helper and component than for logic we > will need to touch only two files and other small settings. By introducing > component to call models, I am also using some what kind of MVC not directly > calling modeles from helpers. > > I will send details explaination soon in the group. > > Thanks for every thing. > > Shadab > > On Sat, Aug 1, 2009 at 1:46 AM, Miles J <mileswjohn...@gmail.com> wrote: > > > You are still not understanding what im saying. Either way, its bad > > practice to put component code in helpers, if you are then it means > > your doing it wrong. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
