Hi, I handle something similar using plugins. Each plugin can be an independent application if you like. What I went for was an application "core" that handles the main layout, users and a few global things. Then each plugin just taps into the part of the core it needs or keeps to itself. I just have to make sure I don't accidentally make the core dependent on any one plugin. :)
On Feb 5, 5:41 pm, MagiaMan <[email protected]> wrote: > Hi all, I am considering using Cake for the next version of an app I > have but need to know how i might do something. something i might > call sub-applications? > > ok. I have a php application "suite" that consists of a "desktop" > that loads in other "applications". Many of these applications are > quite big and I would like to keep each in its own app directory but > be able to access them all through the main desktop application. > > the flow right now looks like this: > > Every call is sent through the desktop main file, it determines what > application is being requested, verifies user rights, and loads the > appropriate application. > > So i need something like: > > ...xyz...../StoreFront/Category/View > > Where StoreFront is the application to load, category is the model and > view the action. > > how might i handle this in Cake? > > Happy Baking & Thanks in advance, > > Daryl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
