Add v2 UI screenshots to the README - #5
Conversation
Capture the five Flask pages plus the pour status list against a demo 12-bottle configuration in safe mode, and document each in a new 'The UI' section. Co-authored-by: cmc0619 <cmc0619@users.noreply.github.com>
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (7)
📒 Files selected for processing (1)
Comment |
Greptile SummaryAdds a screenshot-based overview of the v2 user interface.
Confidence Score: 4/5The PR appears safe to merge after correcting the non-blocking inconsistency in the documented page count. The screenshot additions and references are internally aligned, while the overview's claim of five pages conflicts with the seven views documented in the same section. Files Needing Attention: README.md
|
| Filename | Overview |
|---|---|
| README.md | Adds the v2 UI walkthrough, but its stated count of five pages conflicts with the seven documented views. |
| docs/screenshots/configure-v2.png | Adds the configuration-page screenshot referenced by the README. |
| docs/screenshots/drink-detail-v2.png | Adds the drink-detail screenshot referenced by the README. |
| docs/screenshots/menu-v2.png | Adds the menu screenshot referenced by the README. |
| docs/screenshots/motor-controls-v2.png | Adds the motor-controls screenshot referenced by the README. |
| docs/screenshots/pour-v2.png | Adds the pouring-status screenshot referenced by the README. |
| docs/screenshots/suggestions-v2.png | Adds the first suggestions-page screenshot referenced by the README. |
| docs/screenshots/suggestions2-v2.png | Adds the second suggestions-page screenshot referenced by the README. |
Reviews (1): Last reviewed commit: "Add v2 UI screenshots to README" | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
|
||
| ## The UI | ||
|
|
||
| Flask serves five touch-sized pages at `http://<pi-address>:5000`. The shots |
There was a problem hiding this comment.
The overview says Flask serves five pages, while the section immediately documents seven distinct pages, giving readers an inconsistent description of the UI.
| Flask serves five touch-sized pages at `http://<pi-address>:5000`. The shots | |
| Flask serves seven touch-sized pages at `http://<pi-address>:5000`. The shots |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
2 participants
Screenshots of the v2 UI, taken by running this branch. Targets
agent/barrobot-v2-rewriteso they land inside PR #2 rather than onmain.Adds a The UI section to the README covering all five pages plus the pour status list, with filenames suffixed
-v2.Menu
Pouring
Motor Controls
Drink detail, both suggestion views, and the configuration form are in the README.
How they were taken
app.pyon port 5001 with a democonfig.json: 12 slots (gin, vodka, light/dark rum, tequila, bourbon, triple sec, amaretto, kahlua, dry/sweet vermouth, blue curaçao), a pantry of common mixers, a few substitutions, and safe mode on. 73 drinks are makeable, matching the same demo setup onmain.POST /api/position/1followed byPOST /api/rotate/7.config.jsonandrecipes.jsonare gitignored on this branch, so the demo setup is not in the commit.Differences visible against v1
The v2 stylesheet is doing real work here: flash messages are styled rather than falling out as plain bullets, tables and inputs have consistent spacing, and the motor page gained the trusted-position workflow that blocks live movement until an operator establishes the turret's slot.
No application code was changed.