The native layout is not the app's layout: the item should open under the list, not over it #10

New Issue

rays · 2026-09-20T07:16:33-07:00

rays commented

2026-09-20 07:16:33 -07:00

ipx on a wide screen is three panes: the feed list down the left, the item table across the top right, and the item you are reading underneath it, with a grab bar between them. You pick a row and read it without losing the list.

The native interface pushes the item over the list instead, which is what the page does on a phone -- there it is right, and #detail goes position:fixed over everything under 820px. On a Mac it is wrong: the list disappears to read one item and has to be navigated back to, and the layout stops looking like iPodderX.

The table is wrong too. The page has columns -- pinned, title, feed, file, size, published -- each of which sorts, and the native list is a stack of rows with the same facts run together in a subtitle. On a phone that is the right shape and the page agrees, hiding those columns under 820px. On a wide screen it should be a table.

So: regular width gets the feed list beside a table with the reading pane under it, and a divider that can be dragged. Compact width keeps what it has, which already matches the page.

ipx on a wide screen is three panes: the feed list down the left, the item table across the top right, and the item you are reading underneath it, with a grab bar between them. You pick a row and read it without losing the list. The native interface pushes the item over the list instead, which is what the page does on a phone -- there it is right, and #detail goes position:fixed over everything under 820px. On a Mac it is wrong: the list disappears to read one item and has to be navigated back to, and the layout stops looking like iPodderX. The table is wrong too. The page has columns -- pinned, title, feed, file, size, published -- each of which sorts, and the native list is a stack of rows with the same facts run together in a subtitle. On a phone that is the right shape and the page agrees, hiding those columns under 820px. On a wide screen it should be a table. So: regular width gets the feed list beside a table with the reading pane under it, and a divider that can be dragged. Compact width keeps what it has, which already matches the page.

rays added the bug label 2026-09-20 07:16:33 -07:00

rays referenced this issue from a commit

2026-09-20 08:26:06 -07:00

Three panes and a table, and a wash that is a wash (#10, #12)

rays commented

2026-09-20 08:26:24 -07:00

Done in a13a797. Regular width gets the feed list beside a table with the reading pane under it and a draggable divider; compact keeps what it had, at the same 820px the page draws the line at. Columns are pinned, title, feed, file, size and published, and sorting one asks the server — sorting the rows on screen would only order the fifty that arrived.

A SwiftUI Table with a sort order needs a comparator on every column, so the status column sorts by read rather than being the one that cannot.

Done in a13a797. Regular width gets the feed list beside a table with the reading pane under it and a draggable divider; compact keeps what it had, at the same 820px the page draws the line at. Columns are pinned, title, feed, file, size and published, and sorting one asks the server — sorting the rows on screen would only order the fifty that arrived. A SwiftUI `Table` with a sort order needs a comparator on every column, so the status column sorts by read rather than being the one that cannot.

rays closed this issue

2026-09-20 08:26:24 -07:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: rays/ipodderx-app#10