Implement filterbuttons on Feeds
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KARL3 |
Fix Released
|
Medium
|
Carlos de la Guardia |
Bug Description
Chrissy has a UI in place and Tres has a backend somewhat in place. Time to merge the two.
On Feeds, the user clicks on a filterbutton ("All", "My Communities", "My Content") and sees differently-
1) The page loads and "knows" (sticky) what is the correct button to set.
2) A URL is constructed that fetches those results via JSON, renders HTML, then starts polling for updates.
3) If the user clicks a different filterbutton, a different URL is constructed, telling the server to return a different pile of data.
Spec
=======
1) Sticky. *If possible*, going to the Feeds tab should "remember" whichever was your last chosen filter, display it as the selection, and use it for the data.
** Throw this out if it takes more than one hour. **
2) Choosing a different pile of data should clear the "last updated" and return the full batch.
3) Make sure the URL constructed from one polling to the next retains the selection.
4) Implement the server side that looks in the request.params for the selection. I believe Tres has already done most of this, just make sure you follow his lead.
5) Make sure clicking the button follows the throbber protocol. Clicking a button starts a request, so the throbber state should be changed to "polling". If you use assign the new URL then call .get_items in the JS, it should handle it all itself.
Changed in karl3: | |
assignee: | nobody → Carlos de la Guardia (cguardia) |
importance: | Undecided → Medium |
milestone: | none → m44 |
status: | New → Confirmed |
Changed in karl3: | |
status: | Confirmed → In Progress |
Changed in karl3: | |
milestone: | m44 → m45 |
Changed in karl3: | |
milestone: | m45 → m46 |
Ran out of hours for the week. Everything works now, but I need to fix tests to mark this finished.