So… I finally got bored with Nautilus.
Ubuntu has been my daily driver for the last several years. I remember when Linux used to be a second-class citizen in the desktop space, only used by nerds and devs who could unravel its arcane and obscure mysteries. But it has come a long way. Not only is it a lot more user-friendly with a plethora of customization options, but Steam, and especially Proton, has added first-class gaming support for Linux. I haven’t had a dual boot Ubuntu/Windows system in quite a while and that’s a huge win.
Write Your Own Imaging Processing UI in 15 Minutes, Using Kotlin and Compose for Desktop
Compose used to be just a smooth way of writing Android Applications in Kotlin. Now JetBrains has ported Compose to the Desktop, and it's now easier than ever to prototype UI in real-time.
Of course, you can write a web app-based UI or a single-page application, but sometimes, especially in the IoT world, and a small cluster of Raspberry Pis, the easiest way is to have actually a small Desktop UI.
Distribution of JVM Desktop Applications
The previous posts of this series focused on different frameworks to develop JVM-based applications.
- The state of JVM desktop frameworks: Introduction
- The state of JVM desktop frameworks: Swing
- The state of JVM desktop frameworks: SWT
- The state of JVM desktop frameworks: TornadoFX
- The state of JVM desktop frameworks: Jetpack Compose for Desktop
Distributing applications on a couple of computers inside the same company is not an issue. A lot of products are available for automating the pushing of files onto computers. Issues might start to appear when you need to coordinate the deployment across different physical sites.
The State of JVM Desktop Frameworks: Jetpack Compose for Desktop
The previous posts of this series were dedicated to frameworks that adopted the same traditional Object-Oriented-Programming approach. Components were modeled as classes. This week's post is dedicated to Jet Compose for Desktop, the new kid on the block that offers a completely different approach.
- The state of JVM desktop frameworks: Introduction
- The state of JVM desktop frameworks: Swing
- The state of JVM desktop frameworks: SWT
- The state of JVM desktop frameworks: TornadoFX
Getting Your Feet Wet
Originally, Jetpack Compose was a framework for the Android runtime. Compose for Desktop is its port to the JVM.
The State of JVM Desktop Frameworks: TornadoFX
The two previous posts of this series were respectively dedicated to Swing and SWT. This post is dedicated to Tornado FX, which itself is built on JavaFX.
- The State of JVM Desktop Frameworks: Introduction
- The State of JVM Desktop Frameworks: Swing
- The State of JVM Desktop Frameworks: SWT
JavaFX
JavaFX started as a scripting language named JavaFX script. Sun Microsystems intended to use it to compete with Adobe Flex (now Apache Flex) and Microsoft Silverlight to a lesser extent.
The State of JVM Desktop Frameworks: Swing
In the first post of this series, we went through the rise and fall of some of the desktop frameworks, mainly Java ones. This post and the following will each focus on a single JVM framework. To compare between them, a baseline is in order. Thus, we will develop the same application using different frameworks. Will use the Kotlin language because some of the frameworks require Kotlin.
This post focuses on the Swing API.
Revisiting Desktop Linux: Drowning in the Deep End
A few years ago, I wrote about attempting a switch from my 20-year relationship with macOS to Windows and Linux. I ended up switching back to macOS, but as I was joining the recent throngs of many who felt that Apple was abandoning power macOS users, I was determined to try again.
With recent announcements of the new MacBook Pro 16", the Mac Pro, and Catalina not being as iOS-esque as we all expected, many of our worries are now less so, but still, there were other justifications for a change at the back of my mind.
ArchLinux Tutorial, Part 3: i3 Configuration and Operation
Test Automation Tools for Desktop Applications: Boxed vs. Open Source
Software development practices change over time, and so does the test automation landscape. Today most applications are either web- or mobile-based. The test automation of such systems is well-described. There are some best practices, information-loaded conferences, good tools, and so on. However, we faced a lack of information regarding desktop testing automation, particularly for Windows 7+ apps.
Our task was to test such an application, given that the manual QA process would take more than a month. Here we share the pros and cons of discovered solutions, along with our experience and some best practices of the test automation process.