Right, after a bit of black magic, a few false starts and a fair bit of reworking, djmultipartform is actually working as its meant to more than just an abstract concept which i posted last time. <ul> <li>www.halfapenguin.com/djmultipartform-0.1.tar.gz</li>
<li>www.halfapenguin.com/djmultipartform-0.1.zip (in case someone doesn't have the tools to unzip tar.gz).</li> </ul> There have been a few changes in the way the system works. <ol> <li>there is now a complete method which is accessed through the /complete (overidable when implementing a multipartform), this should be implemented as complete_action.</li> <li>Each page descriptor can have assigned a method to generate a view, which has passed in the the slug, the_form request, and the filter variable. This updates the info_dict passed to the template, by default the method passes an empty dict</li> <li>Stored files can be deleted by a post request to the page with a fieldname and the post variable 'delete' (which should be the fieldname).</li> <li>When a file is uploaded into the store where there is a file already for that field, the old file is deleted and the new file is saved</li> <li> Clear_store now exists and will clear out all the data in the datastore, this should be run as part of the complete method. </li> <li> It is now possible to go backwards without completing form data, however should there be errors in validation of the data on the current page, to avoid confusion the new data for the page will be junked --see below</li> <ol> Future work <ul> <li> adding in behaviour options for the multipartform with respect to moving backwards and junking data </li> <li> Modularise the view code so that components of the view can be overridden. </li> <li> updating the code to use newforms instead of manipulators </li> </ul> --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
