Re: [fw-general] Creating a Modular Dir Structure
Chris, I will be using Zend_ACL and Zend_Layout. What I want to do is separate functionality and html templates for each user group so that I can make updates to the user group's functionality "One user group at a time" since different user group will require significantly different functionality and interface. So for simplicity, upon logging in - the user belongs to a certain group and based on that Group_ID, the front controller only plugs into the controllers and views etc...of that particular module ( based on the Group_ID of the user ). Images, css, javascript can be still under the main public folderall I want to keep separate is the controller/view/scripts/etc I also want to have one area where I can put code that will be used by ALL modules regardless of the User_ID.so that I can reuse code that gives functionality to everyone. Thanks cjant83 wrote: > > Maybe this would be barking up the wrong tree as its vague as to what sort > of application you are creating, and what functionality one user might > have that another doesnt, but I would have thought using Zend_Layout and > Zend_ACL would be better. It seems more logical to me. It could be done > using modules, but I would think it would become a nightmare to maintain. > > Chris. > > > > JDempster wrote: >> >> It sounds plausible to me. You might want to create a >> Zend_Controller_Plugin >> to do it, I'm not sure. Anyone else any ideas? >> >> On Wed, Apr 9, 2008 at 6:21 AM, photo312 <[EMAIL PROTECTED]> wrote: >> >>> >>> I would like to "turn on" controllers dynamically depending on the user >>> logged in...so if the user type logged-in is "client" than it would >>> load: >>> >>> $controller->setControllerDirectory(array( >>> 'default' => '../application/client/controllers' >>> )); >>> >>> this way I can have my modules in different directories and only use the >>> controllers that are residing in the directory that suits the user type. >>> >>> >>> >>> >>> >>> photo312 wrote: >>> > >>> > I have 4 different user groups and each user group will get different >>> > functionality and looks. So I have decided to divide it up into >>> modules >>> > with separate front controllers each. >>> > >>> > Can you please tell me if this modular directory structure would work >>> well >>> > in Zend Framework: >>> > >>> > library/ >>> > ---Zend/ >>> > config/ >>> > public/ >>> > ---index.php >>> > application/ >>> > ---default/ >>> > -controllers/ >>> > -models/ >>> > -views/ >>> > ---scripts/ >>> > ---helpers/ >>> > ---filters/ >>> > client/ >>> > --controllers/ >>> > --models/ >>> > --views >>> > ---...just like above >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16579738.html >>> Sent from the Zend Framework mailing list archive at Nabble.com. >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16610731.html Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Creating a Modular Dir Structure
Maybe this would be barking up the wrong tree as its vague as to what sort of application you are creating, and what functionality one user might have that another doesnt, but I would have thought using Zend_Layout and Zend_ACL would be better. It seems more logical to me. It could be done using modules, but I would think it would become a nightmare to maintain. Chris. JDempster wrote: > > It sounds plausible to me. You might want to create a > Zend_Controller_Plugin > to do it, I'm not sure. Anyone else any ideas? > > On Wed, Apr 9, 2008 at 6:21 AM, photo312 <[EMAIL PROTECTED]> wrote: > >> >> I would like to "turn on" controllers dynamically depending on the user >> logged in...so if the user type logged-in is "client" than it would load: >> >> $controller->setControllerDirectory(array( >> 'default' => '../application/client/controllers' >> )); >> >> this way I can have my modules in different directories and only use the >> controllers that are residing in the directory that suits the user type. >> >> >> >> >> >> photo312 wrote: >> > >> > I have 4 different user groups and each user group will get different >> > functionality and looks. So I have decided to divide it up into modules >> > with separate front controllers each. >> > >> > Can you please tell me if this modular directory structure would work >> well >> > in Zend Framework: >> > >> > library/ >> > ---Zend/ >> > config/ >> > public/ >> > ---index.php >> > application/ >> > ---default/ >> > -controllers/ >> > -models/ >> > -views/ >> > ---scripts/ >> > ---helpers/ >> > ---filters/ >> > client/ >> > --controllers/ >> > --models/ >> > --views >> > ---...just like above >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16579738.html >> Sent from the Zend Framework mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16597984.html Sent from the Zend Framework mailing list archive at Nabble.com.
Re: [fw-general] Creating a Modular Dir Structure
-- photo312 <[EMAIL PROTECTED]> wrote
(on Tuesday, 08 April 2008, 10:21 PM -0700):
> I would like to "turn on" controllers dynamically depending on the user
> logged in...so if the user type logged-in is "client" than it would load:
>
> $controller->setControllerDirectory(array(
> 'default' => '../application/client/controllers'
> ));
I'd instead call this in your bootstrap:
$controller->setModuleDirectory('path/to/application/');
and then write a routeShutdown() plugin that performs the logic
necessary to determine the 'client', and sets that as the current
module in the request:
$request->setModuleName($client);
This will allow you to do:
> this way I can have my modules in different directories and only use the
> controllers that are residing in the directory that suits the user type.
in a more reliable fashion.
> photo312 wrote:
> >
> > I have 4 different user groups and each user group will get different
> > functionality and looks. So I have decided to divide it up into modules
> > with separate front controllers each.
> >
> > Can you please tell me if this modular directory structure would work well
> > in Zend Framework:
> >
> > library/
> > ---Zend/
> > config/
> > public/
> > ---index.php
> > application/
> > ---default/
> > -controllers/
> > -models/
> > -views/
> > ---scripts/
> > ---helpers/
> > ---filters/
> > client/
> > --controllers/
> > --models/
> > --views
> > ---...just like above
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16579738.html
> Sent from the Zend Framework mailing list archive at Nabble.com.
>
--
Matthew Weier O'Phinney
Software Architect | [EMAIL PROTECTED]
Zend - The PHP Company | http://www.zend.com/
Re: [fw-general] Creating a Modular Dir Structure
It sounds plausible to me. You might want to create a Zend_Controller_Plugin to do it, I'm not sure. Anyone else any ideas? On Wed, Apr 9, 2008 at 6:21 AM, photo312 <[EMAIL PROTECTED]> wrote: > > I would like to "turn on" controllers dynamically depending on the user > logged in...so if the user type logged-in is "client" than it would load: > > $controller->setControllerDirectory(array( > 'default' => '../application/client/controllers' > )); > > this way I can have my modules in different directories and only use the > controllers that are residing in the directory that suits the user type. > > > > > > photo312 wrote: > > > > I have 4 different user groups and each user group will get different > > functionality and looks. So I have decided to divide it up into modules > > with separate front controllers each. > > > > Can you please tell me if this modular directory structure would work > well > > in Zend Framework: > > > > library/ > > ---Zend/ > > config/ > > public/ > > ---index.php > > application/ > > ---default/ > > -controllers/ > > -models/ > > -views/ > > ---scripts/ > > ---helpers/ > > ---filters/ > > client/ > > --controllers/ > > --models/ > > --views > > ---...just like above > > > > > > -- > View this message in context: > http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16579738.html > Sent from the Zend Framework mailing list archive at Nabble.com. > >
Re: [fw-general] Creating a Modular Dir Structure
I would like to "turn on" controllers dynamically depending on the user logged in...so if the user type logged-in is "client" than it would load: $controller->setControllerDirectory(array( 'default' => '../application/client/controllers' )); this way I can have my modules in different directories and only use the controllers that are residing in the directory that suits the user type. photo312 wrote: > > I have 4 different user groups and each user group will get different > functionality and looks. So I have decided to divide it up into modules > with separate front controllers each. > > Can you please tell me if this modular directory structure would work well > in Zend Framework: > > library/ > ---Zend/ > config/ > public/ > ---index.php > application/ > ---default/ > -controllers/ > -models/ > -views/ > ---scripts/ > ---helpers/ > ---filters/ > client/ > --controllers/ > --models/ > --views > ---...just like above > > -- View this message in context: http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16579738.html Sent from the Zend Framework mailing list archive at Nabble.com.
[fw-general] Creating a Modular Dir Structure
I have 4 different user groups and each user group will get different functionality and looks. So I have decided to divide it up into modules with separate front controllers each. Can you please tell me if this modular directory structure would work well in Zend Framework: library/ ---Zend/ config/ public/ ---index.php application/ ---default/ -controllers/ -models/ -views/ ---scripts/ ---helpers/ ---filters/ client/ --controllers/ --models/ --views ---...just like above -- View this message in context: http://www.nabble.com/Creating-a-Modular-Dir-Structure-tp16578887p16578887.html Sent from the Zend Framework mailing list archive at Nabble.com.
