web package upload

[dido]

The goal of this task is to allow the users to upload Sophie package that contain book to the server via web UI.

• No additional control should be shown. The exiting one is sophisticated enough to handle this functionality.
• If the package contain book with her linked resources no exeption should be thrown after upload. Success or error massage should be shown.
• At this point no other resources except books could be uploaded, so the package should be listed as book after upload. All linked resources should become part of the database.
• When the package contain Sophie resources, no resources will be uploaded so error message should be shown.
• Add label that explains what things could be uploaded on the server. It may be "Only Sophie books and Sophie package containing book can be uploaded on the server."
• Change the layout of the control so it is more usable. Currently the upload button is too far away from the browse control.
• Change the messages that are shown to be more consistent with the other sections. Use same principle and styles that are used with login functionality.

[deyan]

These two are not clear enough to me:

• Change the layout of the control so it is more usable. Currently the upload button is too far away from the browse control.
• Change the messages that are shown to be more consistent with the other sections. Use same principle and styles that are used with login functionality.

Also, it will be useful the file dialog triggered by "Browse" to have default value *.book.s2 and *.pack.s2

[meddle]

Taking for design...

[meddle]

Closing all the tickets before M Y1