How does this interact with the Accessibility settings on Mac OS?
I haven't tested this on macOS, but it's completely inaccessible with Windows screen readers.
JetBrains Compose
11–20 of 53 posts
Re: JetBrains Compose
#12Ugh, yet another GUI toolkit. Let's spread the work of implementing and debugging accessibility even thinner. I understand that by drawing its own widgets on desktop, Compose can provide greater parity with Android. But that benefits developers at the cost of some users. I think what I would have done is implement the widgets on the web platform and use CEF for the whole application, not just the browser widget. Then…
What's even worse - It's Java UI kit.
Not trying to troll or anything, but what's wrong with Java UI kits?
Re: JetBrains Compose
#13Ugh, yet another GUI toolkit. Let's spread the work of implementing and debugging accessibility even thinner. I understand that by drawing its own widgets on desktop, Compose can provide greater parity with Android. But that benefits developers at the cost of some users. I think what I would have done is implement the widgets on the web platform and use CEF for the whole application, not just the browser widget. Then…
What's even worse - It's Java UI kit.
I know I ranted a bit, but this comment is a shallow dismissal that contributes nothing to the discussion.
Re: JetBrains Compose
#14I started looking into Flutter. Having to code everything in Dart seems to be a stretch. The cross platform UI toolkits should keep the well established composable abstractions - structure / style / script. This trinity provides developer ergonomics, may be we need a layer on top of these toolkits that gets compiled down to code.
Everyone hates XML, but for structuring UI elements it is one of the best tools.
Re: JetBrains Compose
#15My biggest gripe with virtually every UI is that it forces you to learn yet another language just to code with it. Why can't there be UI APIs that work across languages like there is with loads of other stuff? We have this for networking, disk I/O, common OS operations, and even 3D graphics , but for some reason 2D user interfaces just can't be presented in this way. Why can't there be an OpenGL-like thing for deskto…
I agree as a developer, but I think the economics favour having many incompatible UI libraries:
A. It’s expensive to standardise and agree on what the UI primitives would be, and a standard would force the lowest common denominator of features. If you want a new whizz bang button now you have to create an RFC and cajole agreement.
B. It’s profitable to own the platform, which includes the UI, because then you can charge 30% taxes. If Apple spent money making a portable library they would be attacking their own income source.
Re: JetBrains Compose
#16I wish there was a screenshot of a demo app. How do you market a UI toolkit without any screenshots of what I can do? I'm not going to build a demo project to see what the UI looks like.
Re: JetBrains Compose
#17I started looking into Flutter. Having to code everything in Dart seems to be a stretch. The cross platform UI toolkits should keep the well established composable abstractions - structure / style / script. This trinity provides developer ergonomics, may be we need a layer on top of these toolkits that gets compiled down to code. Everyone hates XML, but for structuring UI elements it is one of the best tools.
Not everyone. Give me WPF/WinUI/Android Views and I am good to go.
Re: JetBrains Compose
#18My biggest gripe with virtually every UI is that it forces you to learn yet another language just to code with it. Why can't there be UI APIs that work across languages like there is with loads of other stuff? We have this for networking, disk I/O, common OS operations, and even 3D graphics , but for some reason 2D user interfaces just can't be presented in this way. Why can't there be an OpenGL-like thing for deskto…
I agree as a developer, but I think the economics favour having many incompatible UI libraries: A. It’s expensive to standardise and agree on what the UI primitives would be, and a standard would force the lowest common denominator of features. If you want a new whizz bang button now you have to create an RFC and cajole agreement. B. It’s profitable to own the platform, which includes the UI, because then you can cha…
There's actually an advantage for users. Because you have to enter a new mindset for each platform (or have different devs for each) it pushes you to think about designing the UI to fit the platform. It's nice when the UI and UX feel like they belong with everything else on the system.
Re: JetBrains Compose
#19I ran the samples, the app runs lighter than electron but doesn't feel very native - probably would require a fair amount of styling. I have 200% scaling which worked fine, although I'm guessing some icons should have 2x res to make it crisper.
It's good to have options, and if jetbrains want to pave the way then I just hope they make it fast and with a native feel.
Re: JetBrains Compose
#20I wish there was a screenshot of a demo app. How do you market a UI toolkit without any screenshots of what I can do? I'm not going to build a demo project to see what the UI looks like.
There is if you scroll just a little bit down the page