Re: [fw-general] communicating with forwarded action

2009-04-23 Thread antonM
Hi lightflowmark, thanks for your followup. I appreciate it. =^D Let me explain my point in more detail so you can get a better picture of what I'm trying to do. Below is the directory structure of my module/controllers which I will use to help explain the following details of the project.

Re: [fw-general] communicating with forwarded action

2009-04-23 Thread lightflowmark
Fair enough :-) In my own app, I change the layout on a per-controller basis, using a front-controller plugin, hooking into dispatchLoopStartup(). (You could also choose a layout on a per-module basis, a per-action basis, or any combination of these). If I've understood correctly, this is

Re: [fw-general] communicating with forwarded action

2009-04-23 Thread antonM
Great! Thanks lightflowmark. You got my point and I got yours too. I think the preDispatch method would work for me. I could change the predispatch module/controller/action to the action that will change the layout before the forwarded action is called. In this way, its not anymore necessary to

Re: [fw-general] communicating with forwarded action

2009-04-22 Thread lightflowmark
You can pass parameters as the 4th arg to _forward: $this-_forward('foo', 'bar', 'module',$this-getRequest()-getParams()); antonM wrote: Hi, I was wondering whether it's possible to communicate with the forwarded action in calling the _forward function. for example: class

Re: [fw-general] communicating with forwarded action

2009-04-22 Thread antonM
hi lightflowmark, thanks for your idea. but no, i said i do not want to pass parameters. passing a parameter would mean i have to handle it the parameter from the forwarded action. if i want to change the layout of the forwarded action and pass the layout that should be used then the forwarded

Re: [fw-general] communicating with forwarded action

2009-04-22 Thread lightflowmark
Apologies, I didn't read that last bit before replying. I would still use the parameter array and add a 'layout' value - not sure what you mean by 'don't want to bother its code'. In which case, you need to store the layout variable elsewhere. How about using FlashMessenger, which is