home.social

#waveshare — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #waveshare, aggregated by home.social.

  1. Achei a ideia do #PocketTerm35 da #Waveshare interessante, apesar da ausência de um #trackball, mas a tela de 640x480, apesar de teoricamente adequada, reforça o retrocesso acumulado ao longo de décadas: apesar de todo o blá, blá, blá sobre convergência e dispositivos móveis, a realidade é outra, com desktop environments pesados demais para rodar em SBCs com 1 GB ou 2 GB de RAM (as poucas especificações minimamente acessíveis nos dias de hoje) e, em geral, pouca oferta de software convergente para algo além de relógios, cronômetros e calendários.

    O #GNOME, por exemplo, ainda tem problemas para exibir a grade de aplicativos a 720p, caso o scaling seja de 125% ou maior para tornar a leitura mais fácil em tela pequenas (o que, na prática, reduz a resolução) e, em linhas gerais, parece muito pouco testado para cenários do tipo. E, claro, o GNOME não é exatamente o tipo de ambiente gráfico que você vai rodar num dispositivo, seja ARM, seja x86, com 1 GB ou 2 GB de RAM.

    Mesmo aplicativos mais antigos e fora dos holofotes, como #Abiword e #Gnumeric realisticamente esperam 800x600 de resolução. É compreensível, mas problemático. Simplesmente não temos quase nada que rode em 640x480.

  2. Achei a ideia do #PocketTerm35 da #Waveshare interessante, apesar da ausência de um #trackball, mas a tela de 640x480, apesar de teoricamente adequada, reforça o retrocesso acumulado ao longo de décadas: apesar de todo o blá, blá, blá sobre convergência e dispositivos móveis, a realidade é outra, com desktop environments pesados demais para rodar em SBCs com 1 GB ou 2 GB de RAM (as poucas especificações minimamente acessíveis nos dias de hoje) e, em geral, pouca oferta de software convergente para algo além de relógios, cronômetros e calendários.

    O #GNOME, por exemplo, ainda tem problemas para exibir a grade de aplicativos a 720p, caso o scaling seja de 125% ou maior para tornar a leitura mais fácil em tela pequenas (o que, na prática, reduz a resolução) e, em linhas gerais, parece muito pouco testado para cenários do tipo. E, claro, o GNOME não é exatamente o tipo de ambiente gráfico que você vai rodar num dispositivo, seja ARM, seja x86, com 1 GB ou 2 GB de RAM.

    Mesmo aplicativos mais antigos e fora dos holofotes, como #Abiword e #Gnumeric realisticamente esperam 800x600 de resolução. É compreensível, mas problemático. Simplesmente não temos quase nada que rode em 640x480.

  3. Achei a ideia do #PocketTerm35 da #Waveshare interessante, apesar da ausência de um #trackball, mas a tela de 640x480, apesar de teoricamente adequada, reforça o retrocesso acumulado ao longo de décadas: apesar de todo o blá, blá, blá sobre convergência e dispositivos móveis, a realidade é outra, com desktop environments pesados demais para rodar em SBCs com 1 GB ou 2 GB de RAM (as poucas especificações minimamente acessíveis nos dias de hoje) e, em geral, pouca oferta de software convergente para algo além de relógios, cronômetros e calendários.

    O #GNOME, por exemplo, ainda tem problemas para exibir a grade de aplicativos a 720p, caso o scaling seja de 125% ou maior para tornar a leitura mais fácil em tela pequenas (o que, na prática, reduz a resolução) e, em linhas gerais, parece muito pouco testado para cenários do tipo. E, claro, o GNOME não é exatamente o tipo de ambiente gráfico que você vai rodar num dispositivo, seja ARM, seja x86, com 1 GB ou 2 GB de RAM.

    Mesmo aplicativos mais antigos e fora dos holofotes, como #Abiword e #Gnumeric realisticamente esperam 800x600 de resolução. É compreensível, mas problemático. Simplesmente não temos quase nada que rode em 640x480.

  4. Achei a ideia do #PocketTerm35 da #Waveshare interessante, apesar da ausência de um #trackball, mas a tela de 640x480, apesar de teoricamente adequada, reforça o retrocesso acumulado ao longo de décadas: apesar de todo o blá, blá, blá sobre convergência e dispositivos móveis, a realidade é outra, com desktop environments pesados demais para rodar em SBCs com 1 GB ou 2 GB de RAM (as poucas especificações minimamente acessíveis nos dias de hoje) e, em geral, pouca oferta de software convergente para algo além de relógios, cronômetros e calendários.

    O #GNOME, por exemplo, ainda tem problemas para exibir a grade de aplicativos a 720p, caso o scaling seja de 125% ou maior para tornar a leitura mais fácil em tela pequenas (o que, na prática, reduz a resolução) e, em linhas gerais, parece muito pouco testado para cenários do tipo. E, claro, o GNOME não é exatamente o tipo de ambiente gráfico que você vai rodar num dispositivo, seja ARM, seja x86, com 1 GB ou 2 GB de RAM.

    Mesmo aplicativos mais antigos e fora dos holofotes, como #Abiword e #Gnumeric realisticamente esperam 800x600 de resolução. É compreensível, mas problemático. Simplesmente não temos quase nada que rode em 640x480.

  5. I finally wrapped up my custom mini #cyberdeck build last night. Uses a #waveshare ESP32-S3 touchscreen and a mini "OS" built using #circuitpython I wrote a blog post about the build (including links to download the #3dprint models and code) andywarburton.co.uk/post/gr3ml

    #electronics #diy #maker #esp32 #3dprinting

  6. I finally wrapped up my custom mini #cyberdeck build last night. Uses a #waveshare ESP32-S3 touchscreen and a mini "OS" built using #circuitpython I wrote a blog post about the build (including links to download the #3dprint models and code) andywarburton.co.uk/post/gr3ml

    #electronics #diy #maker #esp32 #3dprinting

  7. I finally wrapped up my custom mini #cyberdeck build last night. Uses a #waveshare ESP32-S3 touchscreen and a mini "OS" built using #circuitpython I wrote a blog post about the build (including links to download the #3dprint models and code) andywarburton.co.uk/post/gr3ml

    #electronics #diy #maker #esp32 #3dprinting

  8. I finally wrapped up my custom mini #cyberdeck build last night. Uses a #waveshare ESP32-S3 touchscreen and a mini "OS" built using #circuitpython I wrote a blog post about the build (including links to download the #3dprint models and code) andywarburton.co.uk/post/gr3ml

    #electronics #diy #maker #esp32 #3dprinting

  9. I finally wrapped up my custom mini #cyberdeck build last night. Uses a #waveshare ESP32-S3 touchscreen and a mini "OS" built using #circuitpython I wrote a blog post about the build (including links to download the #3dprint models and code) andywarburton.co.uk/post/gr3ml

    #electronics #diy #maker #esp32 #3dprinting

  10. PocketTerm35 : un terminal de saisie 3.5″ sous Raspberry Pi
    Le PocketTerm35 combine un écran de 3.5", un clavier QWERTY et les entrailles nécessaires pour accueillir une carte Raspberry Pi..
    minimachines.net/?p=140710 #raspberrypi #waveshare

  11. PocketTerm35 : un terminal de saisie 3.5″ sous Raspberry Pi
    Le PocketTerm35 combine un écran de 3.5", un clavier QWERTY et les entrailles nécessaires pour accueillir une carte Raspberry Pi..
    minimachines.net/?p=140710 #raspberrypi #waveshare

  12. PocketTerm35 : un terminal de saisie 3.5″ sous Raspberry Pi
    Le PocketTerm35 combine un écran de 3.5", un clavier QWERTY et les entrailles nécessaires pour accueillir une carte Raspberry Pi..
    minimachines.net/?p=140710 #raspberrypi #waveshare

  13. PocketTerm35 : un terminal de saisie 3.5″ sous Raspberry Pi
    Le PocketTerm35 combine un écran de 3.5", un clavier QWERTY et les entrailles nécessaires pour accueillir une carte Raspberry Pi..
    minimachines.net/?p=140710 #raspberrypi #waveshare

  14. PocketTerm35 : un terminal de saisie 3.5″ sous Raspberry Pi
    Le PocketTerm35 combine un écran de 3.5", un clavier QWERTY et les entrailles nécessaires pour accueillir une carte Raspberry Pi..
    minimachines.net/?p=140710 #raspberrypi #waveshare

  15. PocketTerm35 is a Raspberry Pi-powered handheld with a 3.5 inch screen and QWERTY keyboard

    Waveshare’s new PocketTerm35 is a handheld computer with a 3.5 inch, 640 x 480 pixel touchscreen IPS display, a 67-key keyboard for thumb typing, dedicated buttons for gaming, and a stereo speaker.

    Designed to use a Raspberry Pi for brains, the system also has four USB Type-A ports, Gigabit Ethernet, a microSD card reader, headphone jack, and support for Raspberry Pi OS and other Linux-based […]

    #handheldPc #pocketterm #pocketterm35 #raspberryPi #raspberryPi4 #raspberryPi5 #waveshare Read more: liliputing.com/pocketterm35-is
  16. PocketTerm35 is a Raspberry Pi-powered handheld with a 3.5 inch screen and QWERTY keyboard

    Waveshare’s new PocketTerm35 is a handheld computer with a 3.5 inch, 640 x 480 pixel touchscreen IPS display, a 67-key keyboard for thumb typing, dedicated buttons for gaming, and a stereo speaker.

    Designed to use a Raspberry Pi for brains, the system also has four USB Type-A ports, Gigabit Ethernet, a microSD card reader, headphone jack, and support for Raspberry Pi OS and other Linux-based […]

    #handheldPc #pocketterm #pocketterm35 #raspberryPi #raspberryPi4 #raspberryPi5 #waveshare Read more: liliputing.com/pocketterm35-is
  17. PocketTerm35 is a Raspberry Pi-powered handheld with a 3.5 inch screen and QWERTY keyboard

    Waveshare’s new PocketTerm35 is a handheld computer with a 3.5 inch, 640 x 480 pixel touchscreen IPS display, a 67-key keyboard for thumb typing, dedicated buttons for gaming, and a stereo speaker.

    Designed to use a Raspberry Pi for brains, the system also has four USB Type-A ports, Gigabit Ethernet, a microSD card reader, headphone jack, and support for Raspberry Pi OS and other Linux-based […]

    #handheldPc #pocketterm #pocketterm35 #raspberryPi #raspberryPi4 #raspberryPi5 #waveshare Read more: liliputing.com/pocketterm35-is
  18. PocketTerm35 is a Raspberry Pi-powered handheld with a 3.5 inch screen and QWERTY keyboard

    Waveshare’s new PocketTerm35 is a handheld computer with a 3.5 inch, 640 x 480 pixel touchscreen IPS display, a 67-key keyboard for thumb typing, dedicated buttons for gaming, and a stereo speaker.

    Designed to use a Raspberry Pi for brains, the system also has four USB Type-A ports, Gigabit Ethernet, a microSD card reader, headphone jack, and support for Raspberry Pi OS and other Linux-based […]

    #handheldPc #pocketterm #pocketterm35 #raspberryPi #raspberryPi4 #raspberryPi5 #waveshare Read more: liliputing.com/pocketterm35-is
  19. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  20. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  21. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  22. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  23. Hello #Smarthome community!
    I finally found the "sweet spot" for displaying data on larger LCDs.

    After testing various layouts (from free-floating icons to strict tables) modern "tiles" are definitely the winner.

    The aesthetics can always be tweaked, but from a functional standpoint, this layout is unbeatable.

    The heart of this project is the #Waveshare ESP32-S3-Touch-LCD-4.3B. It is used as a central dashboard for sensor data and remote control of my other IoT nodes

    #ESPHome #DIY #IoT #LVGL

  24. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  25. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  26. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  27. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  28. After two solid days of wrestling with toolchains, I can now write to the screen. I feel like this is a major accomplishment. Screen refresh is noticeably slow, though.

    I'm using VSCodium, PlatformIO, ESP-IDF, and an ST7789 driver of unknown provenance (probably Waveshare). That's not the first combo I tried, nor the fourth.

    🧵 10/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL #VSCodium #PlatformIO

  29. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  30. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  31. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  32. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL

  33. I'm reviving this project.

    This is the ESP32 board I'm using. It has an ESP32S3, 8+16MB PSRAM, touch screen, yada³. Nice little kit.
    waveshare.com/wiki/ESP32-S3-To

    I am trying to decide whether to use a high level toolkit like LVGL or roll my own optimized SPI driver for the display and eke out all the performance I can. I'm leaning toward the latter, because that's what I always do.

    🧵 9/N

    #ReactionDiffusion #ESP32 #WaveShare #LVGL