upload-permissions

[dido]

The goal of this task is to allow users to upload books on the server and set permissions to them via web ui.

• The upload controls look too far one from another and don't seem like one control. The upload button is too far away from the browse button.
• Add radio buttons for book permissions after the browse control.
  • No rights - in default state this radio button is selected
  • Read rights
  • Read and write rights
• Also when a book is uploaded from the web ui, it's not listed anywhere - fix this. The reason may be that no one have read rights over this book.
  • The book should be visible inside browse section in the web ui
  • The book should be visible inside the client.
  • NOTE. Users should see certain book only if he have read or write rights over the book.

[todor]

maybe the last point is not correct and should be removed, the books are visible from the web ui, not sure if it is part of this task to make them display according to the user rights (e.g. only the books that the user has rights for to be displayed, when he/she is logged)

[mira]

Upload Resource

Extract a common method at the ResourceDirectoryH to be used for uploading resources. (At this point they are only books.) This method should change the security permissions and add a given resource to a server directory. It would be used in both author and web for uploading resources with permissions.

The method should take as arguments:

• ResourceDirectoryH - the main server directory for resources.
• the ResourceAccess - access to the uploaded resource.
• ResourceRefR4 - the ref of the user that is uploading the resource
• The SecirityPermission level for the default group of users.
• The Facade to be user for rewriting the server model of the resource.

WEB UI

Move the submit button (labeled 'Upload') closer to the browse control.
Add a radion button group in the resource_directory.jspx that should act as the permission buttons in the server upload dialog.
Change the UploadResourceHandler to check those permissions and upload the resource accordingly.

[mira]

This patch contains only desing related code.

[meddle]

• Short, clean, good design.
• Don't forget to take out five or more AutoActions for the implementation.
  • The packets you must move them should be named "actions" and will be in the corresponding module of the action.
  • It is better to take out actions only for one module.
  • And it is better to be your own actions.

4p

[mira]

The implementation is done according to the design in the [browse: branches/private/mira/webPermissions]

• I will not be extracting AutoActions in this task.
• I made the ResourceRenderers to be registered to an extension point:
  • I made ResourceRendererProvider interface with four methods - getKind(), getAction() and getRenderer() by given ResourceH and getSortKey().
  • The ResourceRendererFactory just checks for the first action that is with the appropriate kind and action.
  • The logic from the switch is moved to the renderer providers for delete, download and view.
  • There is different logic only for the directory renderer. It creates a list of all visible resources for the currently logged in user. For them I made a simple immutable class ResourceItem.

[pap]

• Commited in [9187].
• I find it strange that the ResourceDirectoryH.uploadToDirectory has two AutoActions in it
• In the same method I find the boolean isUpload parameter a bit strange as there are two other parameter that can be used to comput this.
• You submitted code with warnings about missing JavaDoc. So 3p

[meddle]

Closing all the tickets before M Y1