On 12/19/05, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > (c) the new edit-inline interface will rely heavily on Javascript > (AJAX) to do its job.
How do you envision Ajax use for the edit-inline interface? Would you be using Ajax simply to return the form widgets for an extra inline object, or would you be using it to actually *save* the related objects to the database? I don't think Ajax should be used to save the object, because that goes against the interface concept of having a big, blue "Save" button that saves changes. Plus, on the "Add" form, you wouldn't be able to add inline objects to the database until you knew what the ID of the main object was -- which would make Ajax inline editing impossible until the "Change" form. Let me know if I'm not making sense. Adrian -- Adrian Holovaty holovaty.com | djangoproject.com | chicagocrime.org
