Thanks for the suggestion. I tried to come up with a workflow, which would minimize the required code changes: - user adds attachments as standard attachments - user selects multiple attachments and finds a new context menu entry: "compress attachments into single zip file attachment" - the attachments will be zipped, removed from the message and the new zip file is added - the zip file can be converted to a cloud attachment - note: after the zip file has been created, the user could be prompted to select a cloudfile provider for upload, to reduce mouse clicks This would add general zip capabilities to the composer and would not require changes to the cloudFile code. How does that sound?
Bug 1856232 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for the suggestion. I tried to come up with a workflow, which would minimize the required code changes: - user adds attachments as standard attachments - user selects multiple attachments and finds a new context menu entry: "compress attachments into single zip file attachment" - the attachments will be zipped, removed from the message and the new zip file is added - the zip file can be converted to a cloudFile attachment - note: after the zip file has been created, the user could be prompted to select a cloudFile provider for upload, to reduce mouse clicks This would add general zip capabilities to the composer and would not require changes to the cloudFile code. How does that sound?