When I said "user", I actually meant "developer", "django user"... sorry for the confusion :]
When pre-filling the form to display the "clone" page we can provide a method the developer can override to copy the files on disk, or change anything he wants (for example, change unique fields like slug, since the user will have to edit anyway) But it's possible to implement as Thomas suggested, just provide a new reference for the same file on disk by default, and let the developer choose to copy or not. I'll work on an implementation for this. Thanks for the feedback! Igor. On Wednesday, February 22, 2012 12:04:12 PM UTC-2, juanpex wrote: > > That's it. I only identify this 2 behaviour. > Now, the question is: when and where put this decision the user? > A like ligthbox before copy on click button "clone"?, or in the new > page displaying the cloned object? > I don't know :) > > Regards, > > On Wed, Feb 22, 2012 at 11:53 AM, Igor Sobreira wrote: > >> Yes, that's what I wanted to say. We can decide that this behavior is >> fine by default, document it, and provide an easy way (with callback and >> helper functions) to allow the user to clone the file on disk. > > > > > -- > juanpex > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/dJcLD6P_e90J. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
