5
Qt Bridges: Public Beta for the Rust Bridge Is Out! (www.qt.io)
submitted 4 months ago by to c/qtframework@programming.dev
1 comment fedilink hide all child comments

1 comment

sorted by: hot top controversial new old
[–] 1 point 4 months ago

I've been waiting for some news on this. Can't wait to try it out!

  • permalink
  • fedilink
  • source
    •
    9 comments in c/rust@programming.dev view that post
    [–] 8 points 4 months ago* (5 children)

    Freaking about time they did something like that. Everyone looking for GUI alternative frameworks to run away from eletron and people find qt only to realize that it's impossible to use because you'd have to use that weird cpp language or use python for the only reasonable alternative they support.

    Maybe they were scared of the work Slint is doing.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 1 point 4 months ago (4 children)

    Maybe they were scared of the work Slint is doing.

    What work?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 4 months ago (2 children)

    Being rust native with a ui language like qml and showing all their things working with 3 or 4 languages every release.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 4 months ago* (1 child)

    Well yeah, but I would want to use Qt/QML to have native integration with something like KDE Plasma.

    Unfortunately Slint just recently announced that they will be slowly deprecating the native styles except Fluent, which is Windows's useless and unused style: https://slint.dev/blog/default-native-style-change

    So it is quite good to have this Qt Bridge for Rust.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 4 months ago

    Yeah that part from them was very disappointing. I was really hoping for the qt style integration to be maintained. I really want to do something that integrates well in our plasma/kde environments but don't want to touch those weird languages to do it.

    Hoping this new approach from qt is successful. They tried to maintain others like qt jambi but that is kinda of abandoned or wtv.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 4 months ago

    Slint is pretty much the spiritual successor to QtQuick. I think it's written by people that used to work for Qt, it has a similar design (GUI focused DSL with automatic reactivity), and they are even using the same business model - basically free except for embedded use (cars, petrol pumps, PoS etc.). But without the decades of baggage Qt has and with support for Rust from day one.

    It can even use Qt as a backend somehow.

    I had a go with Slint because it does look impressive but tbh the amount of setup you have to do is just a bit too much compared to something like gpui-component. Probably worth it for a bit project I guess.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 2 points 4 months ago (2 children)

    Couldn't find any info, so maybe someone here knows: Is QT statically linkable, in particular when used from Rust? That's something that I really value in fltk.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 2 points 4 months ago (1 child)

    Not really in practice. In older versions I have done it, but they really don't want you to. The binaries are only distributed as shared libraries, so you at least need to build Qt from source. And also whenever I build recent Qt apps even with QtWidgets it has a load of plugin files and other nonsense that it needs.

    I'm sure it's possible with enough work but it's not simple like with fltk or egui or gpui.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •