Programming Leftovers

posted by Tux Machines on Jul 28, 2022

• Caolán McNamara: GTK4: Toolbar popups via GtkPopovers

  Bootstrapped using GtkPopovers to implement popups from LibreOffice's main menubars for GTK4.

• You should use ReadonlyArray in your React state | Tiger Oakes

  If you’ve ever written any React code, you’ve probably used arrays to represent state: an array of todo items, articles fetched from the server, and more. But sometimes React doesn’t update after you change that state. Usually, that’s because you mutated an array instead of copying it - a mistake easily prevented by using read-only types like ReadonlyArray. Here’s why you should start switching to read-only!

• React Studio: A Real-time RAD Editor and Prototyping tool for React Developers and Designers

  React Studio is a free IDE and RAD tool for designers and developers that allows them in designing, prototyping, and building production-ready React apps.

  The app is currently available for macOS 10.12 and later, it supports dynamic data, and comes with a rich and advanced visual layout editor.

  React Studio supports progressive web apps (PWA) out-of-the-box, which work seamlessly on mobile platforms such as iOS, Android, as well as Chromebooks.

• A toy remote login server

  Hello! The other day we talked about what happened when you press a key in your terminal.

  As a followup, I thought it might be fun to implement a program that’s like a tiny ssh server, but without the security. You can find it on github here, and I’ll explain how it works in this blog post.

  the goal: “ssh” to a remote computer

  Our goal is to be able to login to a remote computer and run commands, like you do with SSH or telnet.

  The biggest difference between this program and SSH is that there’s literally no security (not even a password) – anyone who can make a TCP connection to the server can get a shell and run commands.

  Obviously this is not a useful program in real life, but our goal is to learn a little more about how terminals works, not to write a useful program.

  (I will run a version of it on the public internet for the next week though, you can see how to connect to it at the end of this blog post)

• Android Shared Storage Qt Wrapper - KDAB

  In this article, I’d like to talk about Android storage.

  In recent Android versions, Google decided, for a good reason, to restrict the access to the SD card. This means, even if your application will have the old READ/WRITE_EXTERNAL_STORAGE permissions declared and granted, you won’t be able to freely access the SD Card contents like you used to.

  In order to access the SD card or any other shared storage places, you’ll have to use the Android shared storage API. The good news is that, with this API, you’ll be able to access any file from any storage location (i.e. from gdrive), without any special code.

• Hackster's FPGAdventures: Experimenting with Microchip's PolarFire SoC Icicle Kit Linux Code Samples - Hackster.io

  In our last look at Microchip's flexible PolarFire SoC Icicle Kit, which blends low-power high-performance field-programmable gate array (FPGA) technology with Linux-capable processing cores built around the free and open source RISC-V instruction set architecture (ISA), we built our own Linux distribution using the Yocto board support package (BSP) and ran a selection of workloads to put the system through its paces.

  The Icicle Kit isn't designed as a single-board computer you just pick up and use to run pre-built binaries, though: it's a development tool first and foremost, and whether you're a professional or a hobbyist you're going to want to get your hands dirty coding in order to make the most of the board's capabilities.

• Going to Akademy! | espidev

  I am going to be attending Akademy 2022 in person!

  This is my first time going to Akademy in-person, so it is quite exciting! I will be doing a talk with Bhushan on the state of Plasma Mobile.

  [...]

  Through 2020, I worked on many Plasma Mobile applications such as KWeather, and also started poking around contributing to the shell. I also did some work for the desktop, including some work on adding fingerprint support to the users kcm.

• Nibble Stew: That time when I accidentally social engineered myself to a film set

  I spent the last week in Toronto in the Cpp North conference. It was so much fun just to hang around with people after such a long pause.My talk was about porting large code bases from one build system to another, using LibreOffice as an example The talk should eventually show up on Youtube but there is no precise schedule for that yet.

  After the conference ended I had a few spare days to do touristy stuff which was also fun. On the last day when I was packing my stuff I noticed that there was a film crew just outside the conference hotel clearly shooting something. The area did not seem to be closed off so obviously I went in to take a closer look. It was past 9 pm and I only had my phone camera so all the pictures below are a bit murky. On the other hand you can clearly see just how much lighting power you need to shoot high quality video material.

  [...]

  I stood next to one of the pillars shown in the middle of the picture next to a thing that looked suspiciously like a director's chair. I just leaned against the wall perfectly still while remaining calm and passive and nobody paid any attention to me at all. I could observe the crew going about their business, browse their monitors (which, sadly, did not show anything interesting) and even see their uncannily realistic looking baby prop up close. I was probably there for around 30 minutes or so until someone finally asked me if I was part of the crew and then kindly asked me to leave which I did.

• Common GLib Programming Errors – Michael Catanzaro's Blog

  Let’s examine four mistakes to avoid when writing programs that use GLib, or, alternatively, four mistakes to look for when reviewing code that uses GLib. Experienced GNOME developers will find the first three mistakes pretty simple and basic, but nevertheless they still cause too many crashes. The fourth mistake is more complicated.

  These examples will use C, but the mistakes can happen in any language. In unsafe languages like C, C++, and Vala, these mistakes usually result in security issues, specifically use-after-free vulnerabilities.

• This Week In Rust: This Week in Rust 453