Figured out that while angular tries to destroy the isotope directive scopes the relayout method is being triggered for every call of $scope.destroy(). Since every isotope element will be destroyed when you try to change the view eg. when you are navigating away form the route which is using the isotope directives.
This leads to relayout call equal to the number of elements that are currently visibile on the view.
I tried it with some 50 elements and it was already taking few seconds to complete the destroy+relayout process.
Is there a way to avoide this in angular?
there was a way around for non angular implementation. https://github.com/metafizzy/isotope/issues/195#
which did not work with the angular because it was $.remove() ing the elements which is not acceptable in angular.
Figured out that while angular tries to destroy the isotope directive scopes the relayout method is being triggered for every call of $scope.destroy(). Since every isotope element will be destroyed when you try to change the view eg. when you are navigating away form the route which is using the isotope directives. This leads to relayout call equal to the number of elements that are currently visibile on the view. I tried it with some 50 elements and it was already taking few seconds to complete the destroy+relayout process. Is there a way to avoide this in angular?
there was a way around for non angular implementation. https://github.com/metafizzy/isotope/issues/195# which did not work with the angular because it was $.remove() ing the elements which is not acceptable in angular.
thanx