Talk:River-classic
Latest comment: 10 January by SpotTheZebra in topic rename page to River Classic (Window Manager) and create new page for river (Compositor)
rename page to River Classic (Window Manager) and create new page for river (Compositor)
River recently went from a unified compositor + window manager to strictly a compositor allowing developers and end users to create / user multiple window managers Efog4 (talk) 20:02, 9 January 2026 (UTC)
- Rename of existing page to River Classic is appropriate, but Window Manager suggests X11 and seems unnecessary. New page for upcoming v0.4 will be needed. SpotTheZebra (talk) 20:14, 9 January 2026 (UTC)
- That makes sense colloquially, although river is moving forward with using the term window manager for programs that manage windows using the river protocol despite being built on wayland so on a technical level this may lead to confusion unless clearly explained in the body of one or either of the pages. I do agree though river classic (window manager) is a bit too wordy regardless Efog4 (talk) 02:56, 10 January 2026 (UTC)
- The window manager explanation makes most sense on the new River page. Having looked through the Codeberg page, I see what you mean about its usage, but it is specific to the new compositor. River Classic usually refers to 'layout generators', so I think we should keep 'window manager' out of that page. SpotTheZebra (talk) 15:53, 10 January 2026 (UTC)
- That makes sense colloquially, although river is moving forward with using the term window manager for programs that manage windows using the river protocol despite being built on wayland so on a technical level this may lead to confusion unless clearly explained in the body of one or either of the pages. I do agree though river classic (window manager) is a bit too wordy regardless Efog4 (talk) 02:56, 10 January 2026 (UTC)