Hi JoC For me one of the things I like most about cake isn't so much managing all the associations (although that is very nice (indeed)) it is the fact that the rigid MVC structure makes it easy to find bits of code because everything has its own place in the structure and is logically organised.
I think one of the main benefits is just that you don't 'loose' bits of code - if things aren't where you think they would be they are normally pretty easy to find (e.g. just moved into a component / element / helper etc.) John On Apr 29, 3:10 pm, JoC <[EMAIL PROTECTED]> wrote: > Hello all, > I am trying to write a maintenance software for a generator > distributing company. > The company works the following way > > 1 site has many generators > 1 generators has 1 manufacturer and many parts > 1 part has many generators > 1 manufacturer has many generators and many models > 1 model has one manufacturer > 1 part works for many generators > 1 manufacturer makes many models > . > . > . > > Anyways as you can see is a very complex system. To which then we will > add work orders, maintenance, etc.. > My questions is, will cake PHP make my life easier or harder I have > been working with it for about 1 week and so far its been ok until I > introduced the above concept today of many parts to many generators > etc then it got really complex. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
