Another victory for MaterialFX... #340
palexdev
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone, I hope you're all doing well. I'm currently savoring the last weeks of my vacation, and it's only recently that I've seriously resumed my work on MaterialFX.
There are numerous issues, questions, and contributions that I'd love to address, but my primary focus is elsewhere. I must admit that support for the main branch of MaterialFX is currently at a minimum from my side because I'm giving my undivided attention to the rewrite branch. I am determined to complete this huge project, even though, at the moment, it can only be considered as being in "early access." There is an immense amount of work left to do, including designing, improving, and reviewing APIs, refactoring and implementing components, writing stylesheets, and discovering and resolving bugs.
I want to assure you all that I am dedicated to delivering the new MaterialFX, which I consider to be my masterpiece. I anticipate some major changes coming soon (hopefully next week) on the rewrite branch, so please stay tuned!
Let's shift the focus away from the project for a moment. The primary reason for my message today is to present something to you...
Have you ever found yourself working with JavaFX Labels and thought something like, "Crap, I don't want the text to be cut off, but it seems there's no way to prevent it!"
I certainly have! And I'm aware that you can set the TextOverrun to CLIP, but even then, the result can look quite unappealing in specific situations.
F... you JavaFX 🙂
As you can see, I created a simple Label restricted to be at max 50px in width (the red border helps visualize its bounds). In normal conditions, you would see the text truncated. This changes now with MaterialFX, you're welcome haha
You might be wondering why this feature is important. Well, there are specific situations where you may find this behavior necessary. Moreover, even if it's not always a clear-cut necessity, I would still argue that it's about empowering the user.
You see, one of the things that has always bothered me about JavaFX is its "closed" nature—it can feel overly restrictive. With its private APIs and final methods, advanced users often find themselves having to conform to the framework, with little room for flexibility or customization.
And in response to this behavior, I have always said: "My way or fuck you"
After all, this determination to provide an alternative is one of the key motivations behind the existence of MaterialFX.
Beta Was this translation helpful? Give feedback.
All reactions