Conversation

Notices

1. Embed this notice
   Angle (angle@anticapitalist.party)'s status on Monday, 16-Dec-2024 06:59:55 JST Angle

   • Cybernetic⚡Datapredator

   @lightspill Mmm, I have mixed feelings. Wouldn't mind having, like, stages of UI or something? So it starts out simple, and then there's a config option to ratchet up complexity? Which itself adds complexity, but, so it goes. XD

   • Embed this notice
     wizzwizz4 (wizzwizz4@fosstodon.org)'s status on Monday, 16-Dec-2024 06:59:53 JST wizzwizz4

     in reply to

     @Angle @lightspill We should start with one DE for each paradigm: windowed mouse, tiling keyboard, and single-tasking touchscreen. "Windowed mouse" should be based on Windows 9x (which does, of course, have keyboard combinations), "tiling keyboard" should be based on a good tiling wm (something dmenu-based like dwm or i3, but ideally with mouse support), and "single-tasking touchscreen" should be GNOME 4x-esque but actually good.

     alcinnz repeated this.
   • Embed this notice
     wizzwizz4 (wizzwizz4@fosstodon.org)'s status on Monday, 16-Dec-2024 07:00:22 JST wizzwizz4

     in reply to

     • Cybernetic⚡Datapredator

     @Angle @lightspill Whatever we can abstract from these in a comprehensible way (e.g. most theming, default file associations, consistent key combinations), we should. Where there are already standards (e.g. CSS <system-color>), we should support them, and ideally use them "natively" unless they're somehow wrong-headed (e.g. screen reader APIs implemented over dbus-based RPC).

     It's a lot of work, but it's far from unachievable.