[symfony-users] Re: sfPokaYokePlugin release

2007-07-15 Thread Fabian Lange
Hi Ali, Well done! I see all my wishes included, and what I really appreciate is transparency. It really now works like the server side validation works, it is zero effort to configure anything. Everything I have worked out of the box. Also you reduced the number of files, which reduces complexity

[symfony-users] Re: sfPokaYokePlugin release

2007-07-15 Thread Alistair Stead
Hi Fabian, Glad to hear the plugin is working for you! I plan to work through the performance Unfortunately it is having to do much more work in the filter stack and parse the generate content to find the form action value. If you can suggest another approach then please feel free. On 15/07

[symfony-users] Re: sfPokaYokePlugin release

2007-07-16 Thread Stefan Koopmanschap
Hi Good news about this new release. Let me hit you with a "feature request". I am helping a client get up-to-speed with the Symfony framework and while looking for his "demands", one of them was centralized validation rules. What this means is an app-wide (or maybe even project-wide) yml file in

[symfony-users] Re: sfPokaYokePlugin release

2007-07-16 Thread Lukas Kahwe Smith
Stefan Koopmanschap wrote: > Hi > > Good news about this new release. Let me hit you with a "feature > request". I am helping a client get up-to-speed with the Symfony > framework and while looking for his "demands", one of them was > centralized validation rules. What this means is an app-wide (

[symfony-users] Re: sfPokaYokePlugin release

2007-07-16 Thread Alistair Stead
Hi, Thanks for the suggestions... it sounds like it would be better suited as a seperate filter that writes the action.yml file dynamicly based on the app.yml config. I would not suggest it is a part of the original plugin rather an additional option... feel free to look at the plugin source in S