-sry about those double-quotes! force of habit from other things...
Anteos has done some excellent work on fbackup! - Especially to get recursive folders working properly (using iframes) as if I remember right recursive=1 had some issues.
Some notes for those who are interested:
- Works great on folders - just drag it to the zimlet!
(cartella means folder for those who don't know italian) - Subfolders will even be sorted in your .zip
- It creates a 'backup' folder that works like any other; move messages to it & if you double click the zimlet you'll get the items.zip (or drag the backup folder itself)
- Don't forget you could move your files/folders to the backup folder itself, export them, & move them back out into your normal structure just fine.
- Because you can't 'move' the inbox/junk/sent/drafts/trash I think the right click could be used to solve this - just links to the folders rest url.
- You can drag single messages just the same
- You can only drag one message to it at a time which is fine (though cool of course if this got worked out!)
- Need to make this message more descriptive:
- drop 'Warning'
- 'or folder' isn't needed because you can only drag one folder in zimbra anyway
- I suggest a change to: "You can only export a single message, but consider putting the messages in the backup folder and exporting it, or drag a folder to the Zimlet itself!"
- Error message doesn't appear when you try to drag a conversation to it, so you might think the zimlet isn't working. If we can get it to recognize that your trying to move a convo you could also add: "You may be in conversation view, open up the conversation or switch to message view & grab one at a time."
- Action on dragging an empty folder to it will warn you properly (prototype._FolderDropped)
- However, if you double click the zimlet when the backup folder is empty you instead get a uncaught exception (though hidden) which might make people think the zimlet just doesn't work or something -till they see the mouseover. (ie: need to fix prototype.doubleClicked)
- This should also contain some directions: "It seems you are trying to backup the empty folder 'backup'. Drag and Drop a folder with some contents or an individual message on the zimlet.
- If you already have a 'backup' folder in the first place the 'Cannot create backup folder' etc is not really perfect.
- Instead let's make the folder it creates something easily distinguishable.
- You could use the name of the zimlet itself 'fbackup'. But I'd rather it ends up at the top or bottom of people's structures, not lost in the middle.
- So that rules out BackupFolder FolderBackup as well.
- I guess *fbackup or .BackupFolder or -FolderBackup would work etc (Though I like to avoid symbols because who knows what people will sync up with someday that may complain.)
- Same logic 'middle logic' goes if you want to call the folder BackupZip & zimlet label BackupZipper
- A cool paring would be zipExport & zipExporter
- (ZipBackup combined with ZipperBackup just seemed weird)
- We'll ignore for a moment the hidden error you'll throw if if you delete the folder then double click the zimlet, and you won't see the folder till you reload/plus as part of this you won't see the 'backup folder' till 2nd login after deploying. (This is very livable - when testing just load your browser twice.)
Looking darn good though!
He's not ready to add it to the gallery yet, but throw him a PM if you want to help test.
(Don't know if he wants to post it directly here or not because you are able
able to sell your zimlets; though I hope this one end's up free - because I know it'll make the end user feel better about 'self backups' if they don't use a thick-client or something.)