Update URL with os, revision and arch

[jcfr]

After selecting parameters, the url is not updated.

[zachmullen]

Do you want this to pushState or replaceState? I.e., if the user clicks back, do they iterate through each change they made to the os/revision/arch, or do they go to the page they were on before they entered the app store index page?

[jcfr]

I would like to stick to what the Midas convention would be if any. The
whole midas experience should be consistent.

That said, if not such convention have been defined yet, I think the
"pushState" makes sens. Similar to how the github issue page behave. See
https://github.com/commontk/CTK/issues?state=closed

If you change sort option, or click on "Open" or "Close" .. then click
back, it will bring you to the previous state.

Ideally, we should be implemented in Midas core so that it could benefit
the entire framework. Let me know if generalizing this it is feasible.

Thanks
Jc

On Fri, Apr 19, 2013 at 1:44 PM, Zach Mullen [email protected]:

Do you want this to pushState or replaceState? I.e., if the user clicks
back, do they iterate through each change they made to the
os/revision/arch, or do they go to the page they were on before they
entered the app store index page?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-16668552
.

+1 919 869 8849

[zachmullen]

I don't think we want to do this generally in Midas. There are a lot of client-side javascript application frameworks that build this in automatically such as Backbone.js or ember.js. Generalizing this across Midas should happen when we eventually move to a framework that has already solved the problem :)

[jcfr]

Sounds good. In that case, it makes sens to implement a specific solution.
That said, it there are already code doing such things in midas .. let's
make sure to re-use it.

Thanks
Jc

On Fri, Apr 19, 2013 at 2:04 PM, Zach Mullen [email protected]:

I don't think we want to do this generally in Midas. There are a lot of
client-side javascript application frameworks that build this in
automatically such as Backbone.js or ember.js. Generalizing this across
Midas should happen when we eventually move to a framework that has already
solved the problem :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/47#issuecomment-16669662
.

+1 919 869 8849