On Dec 21, 3:54 pm, Mike Orr <[email protected]> wrote:
> def resource2(self, name, path, new=True, edit=True, delete=True): > > GET /myresource : view index > GET /myresource/new : new form > POST /myresource/new : new action > GET /myresource/1 : view record 1 > GET /myresource/1/edit : edit form > POST /myresource/1/edit : edit action > GET /myresource/1/delete : delete form > POST /myresource/1/delete : delete action I don't like stuff like this, so I could care less. But... If you're going this route, it might make sense to do canned conditions for the most likely implementations, like ned=True would set up new, edit and delete. i've seen that in a few different settings. most notably the Amazon S3 implementation -- where that option really does clean up a lot of code and make it easier to work with. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
