I think that would be a good first approach, yea.

On Jan 18, 2014, at 1:15 AM, Marvin Frederickson <notifications@github.com>
wrote:

In public/frontend_js/screen.js:

> @@ -71,6 +77,18 @@ goog.exportSymbol('concerto.frontend.Screen', concerto.frontend.Screen);
>  concerto.frontend.Screen.prototype.logger_ = goog.debug.Logger.getLogger(
>      'concerto.frontend.Screen');
>
> +/**
> + * Refresh the screen.
> + * Called typically when the content indicates a refresh is warranted
> + * (due to something like a template needing to be changed).
> + */
> +concerto.frontend.Screen.prototype.refresh = function() {
> +  var params = this.getQueryData();
> +  var url = this.refresh_url + '?' + params.toString();
> +  this.logger_.info('Refreshing screen from ' + url);
> +  window.location.replace(url);

So what it sounds like you are saying is that we should not do a
window.location.replace, but work from the screen's current div by wiping
out it's content and starting from there...?

—
Reply to this email directly or view it on
GitHub<https://github.com/concerto/concerto/pull/837/files#r8986675>
.