FileFieldView just works as a wrapper for file field with cross-browser extension.
It could works with SC.Store backend integration.
Backend Integration
Maybe FileFieldView should not on its own integrate with any backend. Instead, autogenerated forms, etc. could handle this logic. Otherwise, logic of where to send the file, etc., would be provided with uploadURL.
The FileFieldView would show the actual <input type="file"> in an iframe, most likely, and would track upload progress through an optional delegate or something like that, perhaps?
Again, auto-generated forms and even the model could perhaps be told what kind of back-end they are dealing with.
With Other Data
How could one allow uploading multiple files, in separate iframes, all to one URL at the same time?
Comments (1)
Charles Jolley said
at 10:32 pm on Oct 30, 2009
This is a great idea. One possible option is that the FileFieldView could provide some kind of SC.Upload object, which can actually be used to submit and upload (tracking progress of the transmission, etc.)
This would mean that when you submit a form, you will probably need to write some code to manually handle uploading of files, but this is almost always what you want anyway so you can show a nice progress bar.
You don't have permission to comment on this page.