by the following rules:
1) An initial dialog or panel load can take either HTML or JSON, but
the mime type must accurately reflect its payload.
2) dialog form submits can handle a pure HTML response, but the mime
type must also be correct. This properly resolves the problem
where the reauth code gets a JSON response first from the reauth
code, and then an HTML response when you reauth and continue on to
a given form -- try it out with Admin > Settings > Advanced.
3) All JSON replies must set the mime type correctly. The json::reply
convenience function does this for us.
4) By default, any HTML content sent back in the JSON response should be
in the "html" field, no longer the "form" field.
The combination of these allows us to stop doing boilerplate code like
this in our controllers:
// Print our view, JSON encoded
json::reply(array("form" => (string) $view));
instead, controllers can just return HTML, eg:
// Print our view
print $view;
That's much more intuitive for developers.
many separate queries.
In the process, rip out the summary column, we weren't using it.
Clean up the test, and drop the exif_records database on uninstall.
However, The text needs to be scaled or the size of the box needs to
be managed such that there is nowrapping. The columns need to be
styled for odd and even. And I can't get tabbing to work. If you
click on details tab nothing happens and i don't know what I've done
wrong. Addition input is appreciated.
