ogoffart

11 ms·

121.
by ogoffart 3y ago
Thank you for your feedback! We are aware of the issue regarding accessibility when rendering via HTML Canvas on the web platform. Our web version of Slint is mainly, as you guessed, designed for demo purposes. While it would be possible to
122.
Show HN: Slint – A declarative UI toolkit for embedded and desktop(slint.dev)
291 points by ogoffart 3y ago|148 comments
123.
by ogoffart 3y ago
> welcome advance on the older techniques such as gettext. I disagree. I think it depends on the use-cases. I blogged about that recently: https://slint-ui.com/blog/translation-infrastructure In short, I much prefer
124.
by ogoffart 3y ago
In the examples you mentioned, the UI is typically described in XML or form files (.dfm), which is essentially a declarative approach, and clearly not described in imperative code. Although they may not be intended to be edited by hand, the
125.
by ogoffart 3y ago
Good point. I don't see the issue with a new syntax either. GUI libraries always come with their own set of large APIs and conventions, so learning a new syntax isn't a big deal. The special tooling and dev environment in Slint ar
126.
by ogoffart 3y ago
It seems you may have used the FemtoVG backend, which is the default if Qt is not installed and is written in pure Rust. We offer multiple rendering backends, and you may have better results with the Qt or Skia backend, which utilize native
127.
by ogoffart 3y ago
I respectfully disagree. In my experience, Declarative UI is more concise, making development and changes easier. It enhances productivity and allows for a clear separation of concerns, which is beneficial. Moreover, Declarative UI enables
128.
by ogoffart 3y ago
Slint dev here. I'm a bit disappointed to see that Slint is considered a non-starter. In fact, one of our users is currently working on exactly that (a VST plugin for an audio application) and they are about to release it very soon. Un
129.
by ogoffart 3y ago
The most complex I know about: https://github.com/gyroflow/gyroflow
130.
by ogoffart 3y ago
- https://github.com/woboq/qmetaobject-rs - https://github.com/KDAB/cxx-qt/
131.
by ogoffart 3y ago
Shameless plug for an alternative to Qt I've been working on: Slint https://slint-ui.com
132.
by ogoffart 4y ago
I'd also like to mention Slint: https://slint-ui.com It is a modern alternative to QML.
133.
by ogoffart 4y ago
I'm trying to solve the native desktop GUI with Slint [1] Our goal is to get native look and feel on every desktop platform, with a great developer experience (and also designer experience). To do that we want the developer to use the
134.
by ogoffart 4y ago
Another one is Slint: https://github.com/slint-ui/slint
135.
by ogoffart 4y ago
The language I designed for Slint [ https://github.com/slint-ui/slint ] uses kebab-case, so it mandates spaces around the minus sign. (If the lookup for `foo-bar` fails, it tries with `foo` and if that succeeds, the er
136.
by ogoffart 4y ago
> As it stands, the standard chess initial position gives white a slight edge, with white usually winning around 55% of game points Could this be explained because this initial position has the most studied and memorized opening. And whi
137.
by ogoffart 4y ago
You forgot to mention [Slint]( https://github.com/slint-ui/slint )
138.
by ogoffart 4y ago
This is about a blog article from 2018 from a attempt to shrink Qt to work on MCU. But since then, the Qt Company has made a new product called "Qt for MCU" which is not the same product at all. The current "Qt for MCU"
139.
Upcoming Changes to the Slint Language(slint-ui.com)
2 points by ogoffart 4y ago|0 comments
140.
by ogoffart 4y ago
With Slint [ https://slint-ui.com ], our aim is to achieve native look and feel, and accessibility.
141.
by ogoffart 4y ago
> Unfortunately, I don't see any big player investing time and money in a nice cross-platform native framework that could offer the same capabilities as Electron. I'm working on Slint: https://slint-ui.com
142.
by ogoffart 4y ago
Slint has had accessibility support before. (But it was arguably done by calling into a C++ library, so technically not pure rust.) https://github.com/slint-ui/slint/pull/1294
143.
by ogoffart 4y ago
Yes, exactly. My point is that the open source project who wants to be a more liberal license can do it, just like KDE did. Then if someone wants to take that for proprietary software, they can do it too, like Apple. They don't even ne
144.
by ogoffart 4y ago
If I was laughably wrong, why are WebKit and Safari not GPL, despite it is based on KHTML which was using Qt 3.x which was GPL. From your argument, Qt's GPL should have "infected" KHTML's code and so WebKit, and by exten
145.
by ogoffart 4y ago
maybe calling a void function with no arguments did not change, but other things changed in various ways making it not stable. What would be the point for the GCC team to even try to be compatible with a changing and non-documented ABI? It
146.
by ogoffart 4y ago
I stand by what I said Because Apache/MIT is compatible with the GPL, it is totally fine for people who like to license their code in Apache/MIT to do so. An example of that is KHTML, the web engine: KHTML was licensed under LGPL,
147.
by ogoffart 4y ago
Maintainer here :-). Would you like to elaborate?
148.
by ogoffart 4y ago
I was working an a library at the time, that was using purely pre-C++11 features, and I remember we had to make a build of the library for each MSVC versions we supported at the time. Because they were not compatible, even for basic stuff.
149.
by ogoffart 4y ago
You can run pretty complex UI already https://www.youtube.com/watch?v=dkBwNocItGs
150.
by ogoffart 4y ago
The ABI is only compatible between versions since MSVC 2015: https://learn.microsoft.com/en-us/cpp/porting/binary-compat-... Also I think the debug and release build are still incompatible.

More ›