View state persitence

[plalx]

As it is right now, when we navigate from a route to another, controllers and views are destroyed. That's having a negative impact on user experience since when you go back to search results, the state is not fully restored (e.g. scroll position and category expand states). Perhaps we could drop the ng-view directive in favor of a simple ng-show directive?

This would probably allow us to drop the shared itemSearchModel service. Another option would be to store the whole view state in a shared service so that it can be fully restored, but that seems overcomplicated.

@daneroo Any thoughts?

[daneroo]

Je n'ai pas suffisament utiliser le routage pour suggerer comment s'en servir simplement, mais je pense que la fonctionalite d'un ng-show ferait l'affaire amplement.

On pourrait re-visiter l'idee d'un route plus stateful, incluant le searchTerm plus tard, surtout si on commencait a faire du tracking des termes de recherche utilises, on si on ajoutait une fonctionalite de sharing (qui inclurait peut-etre un search result...)