Hi, I already wanted to look at hyperadmin, but got caught up reading what HATEOAS is and how it works first ;) I do have one question if you don't mind: With a REST/HATEOS backend you'd export links with appropriate rel attributes to tell the client what we can do. So far so good, but let's pick the template version as example, how does it know where to put which links, does it solely look on rel and figure out what to do with it? Also how do you sensible provide extradata like the _meta information of the model etc…
Which files do you think are a good start when looking at hyperadmin? Thx & Regards, Florian P.S.: I agree that hyperadmin takes a good approach to the admin problem, imo something along this line should power a new admin. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
