Just realised I accidentally sent this to Mike directly instead of the
list.
On 29 Jan 2008, at 23:17, Mike Orr wrote:
>
> On Jan 29, 2008 2:55 PM, Steven Holmes <[EMAIL PROTECTED]> wrote:
>
>> What I was suggesting for @validate would still have two methods on
>> t
On 29 Jan 2008, at 18:51, Mike Orr wrote:
>
> @validate is another issue. It's a nice convenience but it does limit
> what you can do in your code. Going to a one-method scheme would
> require it to be bypassed or rewritten in the application. I've also
> found another problem in that the form
On 29 Jan 2008, at 16:53, Matt Feifarek wrote:
> On Jan 29, 2008 11:21 AM, Mike Orr <[EMAIL PROTECTED]> wrote:
>
> Yes, we're disagreeing on what the default should be. Well, you'll
> have to convince Ben. I think he likes it the other way.
>
> I don't have this particular religion, but what w
On 29 Jan 2008, at 16:21, Mike Orr wrote:
>
> On Jan 29, 2008 3:28 AM, Steven Holmes <[EMAIL PROTECTED]> wrote:
>> In my opinion, it should be *default* do the right thing, which is to
>> have one exposed url for a form. Or at least, the documentation
>> shoul
On 29 Jan 2008, at 11:06, Dmitry Lipovoi wrote:
>
> also in routes it's possible to config one url to diffetent actions on
> GET and POST requests.
> something like this:
>
> m.connect('myform', controller='form', action='handle_form',
> conditions=dict(method=['POST']))
> m.connect('myform', co
On 29 Jan 2008, at 08:36, Alberto Valverde wrote:
>
> Steven Holmes wrote:
>> Hi,
>>
>> @validate supports separating form rendering and form post processing
> into distinct methods. This is convenient, but has a nasty flaw: It
> requires two separate URLs, a form d
Hi,
@validate supports separating form rendering and form post processing
into distinct methods. This is convenient, but has a nasty flaw: It
requires two separate URLs, a form display URL and a URL to handle the
post. When a form post fails to validate, the form is re-displayed,
but at t
On 12 Jan 2008, at 03:35, kapil wrote:
>
> hi folks,
>
> i'm trying to refactor a set of resource controllers to use a common
> base class. all the subclasses need customized validators, and
> authorization but their method implementations are generic. both
> validation and authorization where pr
