If we are honest, we all are desperately awaiting the future. We are waiting for the next boom, which seems so close but actually didn’t come much closer for the last 5 years. Microsoft’s Fluent Design is one of these developments that promise a brighter future. Will it be able to live up to the high expectations of the UI Designer communities? What can designers, what can developers take from it right now? I took a look at the Fluent Design System and explored it during my work on a first test project. In this article, I’ll share what I learned so far.
Thinking Out of the Box
Posts Tagged ‘UI’
This article is intended for developers that are creating and/or maintaining applications with a Java Swing based GUI. Though JavaFX is being pushed as the “new Swing” nowadays, Swing is still around.
Look & Feels are inextricably linked with every Swing application. Even if none is used explicitly, every time, a Swing based GUI is created, a Look & Feel cares about the look and (you may guess it) the feel of what you see and interact with on the screen.
A Look & Feel – so its official title says – is pluggable. This means you can plug a new or different one to your application (strongly simplified, as this actually goes down to the level of a single
JComponent). You may now ask: “But why should I care, if I do not change the Look & Feel now?” In an ideal world, you would not need to care. But, as often when using something, there are contracts.
This is what this article is about. I want to point out why you should care and develop or even maintain your Java Swing GUI or custom component with the pluggable Look & Feel technology in mind.