Hi,
The backpack and trashcan have two different purposes: the backpack is a way for users to save blocks for later, the trash can is more a side effect of blocks having been deleted. That said, I can definitely see how a user would see the two as being similar.
There are a couple of differences you didn’t mention that can affect the user. For example, trashcan contents aren’t persisted when you reload a workspace. Also, the backpack offers some additional features, like Copy all Blocks.
Since the backpack is a plugin, it gets used and extended in ways outside of our control. Some apps built with Blockly use the backpack as a way for users to store blocks and move them across workspaces. I’d be super interested to hear other use cases that folks have found for the backpack.
If there are more features you want to see, you can always feel free to submit a feature request! In the meantime, the backpack already exposes getContents() and setContents() methods. You could use these to implement the import/export from the backpack in your own app regardless of whether that functionality ends up in the plugin.
Best,
Zoë
--
You received this message because you are subscribed to the Google Groups "Blockly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blockly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/blockly/d9ca9f7e-1e71-4101-aec4-f5fe9a5e416fn%40googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/blockly/0ff3e547-f857-4328-8949-bd8f1349265an%40googlegroups.com.