{"action":"created","issue":{"url":"https://api.github.com/repos/steveswinsburg/gradebookNG/issues/98","labels_url":"https://api.github.com/repos/steveswinsburg/gradebookNG/issues/98/labels{/name}","comments_url":"https://api.github.com/repos/steveswinsburg/gradebookNG/issues/98/comments","events_url":"https://api.github.com/repos/steveswinsburg/gradebookNG/issues/98/events","html_url":"https://github.com/steveswinsburg/gradebookNG/issues/98","id":83792174,"number":98,"title":"Section/Group filter","user":{"login":"payten","id":608337,"avatar_url":"https://avatars.githubusercontent.com/u/608337?v=3","gravatar_id":"","url":"https://api.github.com/users/payten","html_url":"https://github.com/payten","followers_url":"https://api.github.com/users/payten/followers","following_url":"https://api.github.com/users/payten/following{/other_user}","gists_url":"https://api.github.com/users/payten/gists{/gist_id}","starred_url":"https://api.github.com/users/payten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/payten/subscriptions","organizations_url":"https://api.github.com/users/payten/orgs","repos_url":"https://api.github.com/users/payten/repos","events_url":"https://api.github.com/users/payten/events{/privacy}","received_events_url":"https://api.github.com/users/payten/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-06-02T02:15:34Z","updated_at":"2015-06-15T23:27:08Z","closed_at":null,"body":"Hi @steveswinsburg,\r\n\r\nJust thought I'd add an issue for this feature.\r\n\r\nI was going to jump in and have a go at implementing this via the Javascript, but quickly realised we haven't surfaced any of the user memberships in the DOM yet.\r\n\r\nIs there a way we can get all the user's memberships quickly?  Or should we perhaps load all the group membership data in asynchronously?\r\n\r\nThanks,\r\nPayten"},"comment":{"url":"https://api.github.com/repos/steveswinsburg/gradebookNG/issues/comments/112236911","html_url":"https://github.com/steveswinsburg/gradebookNG/issues/98#issuecomment-112236911","issue_url":"https://api.github.com/repos/steveswinsburg/gradebookNG/issues/98","id":112236911,"user":{"login":"payten","id":608337,"avatar_url":"https://avatars.githubusercontent.com/u/608337?v=3","gravatar_id":"","url":"https://api.github.com/users/payten","html_url":"https://github.com/payten","followers_url":"https://api.github.com/users/payten/followers","following_url":"https://api.github.com/users/payten/following{/other_user}","gists_url":"https://api.github.com/users/payten/gists{/gist_id}","starred_url":"https://api.github.com/users/payten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/payten/subscriptions","organizations_url":"https://api.github.com/users/payten/orgs","repos_url":"https://api.github.com/users/payten/repos","events_url":"https://api.github.com/users/payten/events{/privacy}","received_events_url":"https://api.github.com/users/payten/received_events","type":"User","site_admin":false},"created_at":"2015-06-15T23:27:08Z","updated_at":"2015-06-15T23:27:08Z","body":"In regards to retaining state on page refreshes, I guess we have a few options:\r\n- store the state on the session and maintain this state via the wicket filters plus some custom javascript to reestablish the state in the browser\r\n- try to avoid page refreshes and let the browsers retain the state where possible\r\n\r\nAt the moment much of the state is established in the browser and we avoid page refreshes by AJAX'ing POSTs and GETs as required.  I understand that may not be possible with the group/section filter and sorting, so to keep the interface consistent upon these page refreshes we may need to store many of these things on the session.  Ideally we'd store which columns are visible, whether categories are enabled, perhaps the currently focused cell and any current error/info messages.  \r\n\r\nPotentially the custom javascript could control all of the state stuff using cookies and querying those cookies upon initialising the page and each of the features.  For me the question is which parts should Wicket handle and where can the custom javascript best pick up the slack."}}