On 8/6/07, David Larlet <[EMAIL PROTECTED]> wrote:
> * What about additional pages like: create form, update form, delete
> confirmation and so on? I've just noticed the get_create_form at the
> end of the TemplateResponder but how can I redirect to this function?
> (I haven't seen how to do this in url generation.)
> * How can I deal with custom forms for a resource?

I extended the template example to include a create form and an update
form [1]. Note that you need something like HttpMethodsMiddleware [2]
in order to use the update form and that the forms are currently not
redisplayed after erroneous input. For any other forms and extensions,
just write views and add the URLs to urlpatterns (above the catch-all
resource URLs). If you feel that the REST interface should support
this kind of work and have ideas how this might look like, please let
me know.

> * Is it possible to specify the format at the end of an url or will it
> break the parsing?

Yes, this is possible if you specify the urlpatterns for collection
and entry individually. I just added such an example [3].

> And last but not least, what is the current stability?

If you can, wait at least until Fri, August 24th before using the REST
interface in any kind of production environment. By then I hope to
have done more thorough testing. If you stumble upon a bug, please let
me know.

Thanks for your feedback.

Regards,
Andreas Stuhlmüller

[1] 
http://django-rest-interface.googlecode.com/svn/trunk/django_restapi_tests/examples/template.py
[2] http://www.djangosnippets.org/snippets/174/
[3] 
http://django-rest-interface.googlecode.com/svn/trunk/django_restapi_tests/examples/fixedend_urls.py

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" 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/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to