Live data from Hacker News

Technical Vision for Qt 6

blog.qt.io

181–184 of 184 posts

Re: Technical Vision for Qt 6

#181
post #136

Earlier quoted context omitted.

I guess you are a JS developer. Some of us have a C++ background and C++ code base. Qt is for us a more natural choice (and has been for a long time) than electron is. "a unknown markup language and toolchain just to get a window displaying" is basically what JS/CSS is for me (is it still hard to get a text center-aligned vertically and horizontally or have they finally gotten over that?) Qt does not force you to use…

> is it still hard to get a text center-aligned vertically and horizontally This has not been true for over 5 years.

Since this discussion I have checked to see if one of the projects I want to do, that requires OpenGL rendering inside an UI, would not be doable with electron.

Google Qt and OpenGL and you get the documentation of the appropriate widget. Google GL and electron and you get a bunch of github issues and people complaining it does not work well yet.

Nah, JS is struggling to get where Qt has been for years. I am happy that it solved its text alignment issue in 2014 though.

Re: Technical Vision for Qt 6

#182
post #159

I'm converting a 500KLOC C++ consumer app from Win32 to Qt so it can also run on macOS. All the app-specific code remains the same. I'm very pleased with how easy it is to design dialogs. Qt is better than anything Microsoft has to offer; what would entice me to forego portability?

Have a try at WPF/WinUI, Blend tooling and the myriad of companies selling ready made components. Otherwise, yes Qt is the best option for cross platform C++ code.

@pjmlp Thanks for the suggestion. I can see using WPF/WinUI for corporate-type apps where it will run under Windows on thousands of desks. However, if WPF/WinUI doesn't run on macOS, there is no incentive to use it for consumer products. When I do customer presentations, the number one question is "When will it run on the Mac?"

Re: Technical Vision for Qt 6

#183
post #61

Earlier quoted context omitted.

I keep coming back to the differences between OPENSTEP and Taligent and believe C++ isn't the best choice.

What were some of the differences? (Other than Taligent dying and OPENSTEP surviving via Mac OS X, which is all I know about the topic.)

https://books.google.com/books?id=e35JCAAAQBAJ&pg=PT139&lpg=...

Gives the basics of the difference

Re: Technical Vision for Qt 6

#184
post #159

Earlier quoted context omitted.

Have a try at WPF/WinUI, Blend tooling and the myriad of companies selling ready made components. Otherwise, yes Qt is the best option for cross platform C++ code.

@pjmlp Thanks for the suggestion. I can see using WPF/WinUI for corporate-type apps where it will run under Windows on thousands of desks. However, if WPF/WinUI doesn't run on macOS, there is no incentive to use it for consumer products. When I do customer presentations, the number one question is "When will it run on the Mac?"

Maybe sooner than we would expect, but it will take a while still.

https://devblogs.microsoft.com/dotnet/calling-all-net-deskto...

Post reply on HN