Closed Bug 729763 Opened 12 years ago Closed 12 years ago

Home screen should display top stacks

Categories

(Pancake Graveyard :: Front-end, enhancement, P5)

x86
macOS
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gbrander, Assigned: gbrander)

References

Details

What I expect:

1. Load app home screen
2. See a list of recently accessed stacks

What happens:

1. Load app home screen
2.See a list of recently accessed sites

We'll have to have some sort of visual treatment for stacks to differentiate them.

There is now an API call to return the top rated sites from a user's browsing history in pancake, and is intended for use on the 'home' screen.

http://play.fxhome.mozillalabs.com:4322/lattice/you@there.com/stack/top_rated

When a user taps on one of the offered stack/place combinations, the front end should send a PUT request to the same API URL.
Priority: -- → P5
Blocks: 729768
Home screen now displays results from /lattice/{username}/stacks/top_rated. https://bitbucket.org/mozillapancake/pancake/changeset/882a11ddd84f.

Additionally, clicking a top stack will:

1. Make a stack:change call via the new Bridge.prototype.changeStack method.
2. Make a place:change call via the new Bridge.prototype.changePlace method.

These methods are meant to deprecate selectPlace and selectStack, which required an inversion of control -- a method needed to be added to Bridge so decorateMessage could be called in order to add a session_id.

Stacks now use the new RESTful APIs, which send back a session_id after POST and PUT requests, so no outside information is needed from Bridge.

The new methods will also throw helpful exceptions when required keys are missing from the message object.
Outstanding issue: TOP needs to notify the drawer of the place:change, stack:change events, so it reflects top stack access.
Depends on: 733664
No longer depends on: 733664
Fixed as of https://bitbucket.org/mozillapancake/pancake/changeset/e30409e0e166
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.