Sadly this is not going to be a straightforward change, and I think we should tackle this after the legacy code has been deleted.

Currently the Bookmarks Service is handling the model, that means that whenever we delete something from the TableView, we asks the service first, and then once the service has deleted the item, it tells the TableView to update itself. 

The updates are pretty generic and don't give the TableView much information, so the TableView pretty much reloads itself completely. This is why we don't have animations, a full reload doesn't produce any.

We need to know which rows/items were deleted so we can delete their rows directly, instead of asking the TableView to recalculate everything which will end up "deleting" those rows since they don't exist in the model anymore. 

In order to achieve this we need to change the way we handle these updates, similar changes were done for the new TabGrid, so I might base myself on that.