It looks good, Thanks for sharing. On Wed, Apr 3, 2013 at 8:41 PM, Jason Kraus <[email protected]> wrote: > > A RESTful api with a separate template client is exactly what hyperadmin > aims to do: https://github.com/zbyte64/django-hyperadmin > I've played around with bolting on an emberjs client or having an admin > powered by django templates and both options can and do work. It pretty much > works as you describe, a CRUD engine operates independently of the > presentation layer but for this to work reasonably links themselves must be > communicated so that filtering, sorting, etc can easily be represented by a > variety of clients. If you don't like the client you can choose or build > another one without having to re-implement the admin operations and logic. > > The focus on HATEOAS also allows for No-SQL storages > (https://github.com/zbyte64/django-hyperadmin-dockitresource) to be used by > the same clients because the functionality emitted by the document store is > described as links. If you want more functionality exposed then it is a > matter of getting your resource to emit the proper links. >
-- Serge G. Spaolonzi Cobalys Systems http://www.cobalys.com -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
