On 4 Aug 2009, at 15:04, Felix Gilcher wrote:
> You certainly can do that. You can modify the FPF settings in the  
> view by modifying the config. The (default) FPF config is stored in  
> the attribute namespace 'org.agavi.filter.FormPopulationFilter' in  
> the requests attributes, so it can be retrieved by calling
>
>               $this->context->getRequest()- 
> >getAttributes('org.agavi.filter.FormPopulationFilter');

That is good to know. Thanks!


>  There is currently no way to do this in the FPF configuration.

That is a shame... I think some way to name FPF configurations,  
similar to how layouts can be named, would be quite useful. Ideally  
for me in the view I would just call a method like "loadFilter" like I  
would call "loadLayout".

Admittedly for a single app it might be a bit strange to have a lot of  
different ways of presenting errors, but on two sites now I have  
wanted to have two different ways of presenting errors (for the same  
output type): one for little one input-element forms in a side-bar,  
and then another for "big" forms taking up a whole page.


Michal.



_______________________________________________
users mailing list
[email protected]
http://lists.agavi.org/mailman/listinfo/users

Reply via email to