Community
Participate
Working Groups
For M5, we want users to be able import files into Orion from the file system and export back out.
We may want to check out http://dojotoolkit.org/reference-guide/dojox/form/FileUploader.html
I just added a link to the nav-table view for export. You can click on "Download as ZIP" to get the contents of a folder as a zip.
(In reply to comment #2) > I just added a link to the nav-table view for export. > You can click on "Download as ZIP" to get the contents of a folder as a zip. Works nice. The only inconvenience is that you leave the IDE when you click on it. I'm looking at the import now.
I have released the first version of the dialog. If you create a folder and go into it, you will see an extra option in the toolbar which opens "Import from zip" dialog. Click "Select File" to choose a file to import and then "Submit". It will do POST on the folder ImportLocation and will send the content. The dialog will not be closed, you need to click "x". I'll fix that tomorrow. I was not able to modify headers. It seems it cannot be done when sending a form. I'll double check that. I'll polish the UI tomorrow with Gosia's help.
Moreover fileMask seems not to work, so you are able to select non-zip files too. It looks like a bug in Dojo.
I have changed the servlet implementation to accept the multi-part form input provided by the dojo FileUpload dialog. Now it assumes the POST contains an entire zip file in the body by default. It will switch to chunked upload only if the X-Xfer-Content-Length header is specified. Some polish items: - Dialog doesn't close when the upload is completed - Navigator tree/table doesn't refresh to show the uploaded content - It will fail if the client doesn't specify a zip file. The failure mode is bad, the browser opens a "Save As" dialog to save the JSON response object describing the failure.
(In reply to comment #6) > - Dialog doesn't close when the upload is completed > - Navigator tree/table doesn't refresh to show the uploaded content Fixed. > - It will fail if the client doesn't specify a zip file. The failure mode is... Investigating.
Basic UI was done for M5. We can open additional bugs for follow-on work.