Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Hello Qt for Python

blog.qt.io

Post reply on HN
Print view View original

171–176 of 176 posts

Re: Hello Qt for Python

#171

Post by nadioca »

JasonFruit wrote: post #157
nadioca wrote: post #127

Earlier quoted context omitted.

more exactly “underlying C/C++ object has been deleted" error.

In my experience, those errors are easy to resolve: just assign the new object to something, so it isn't immediately deleted. A little awkward, maybe, and it shouldn't happen, but if that's the worst quirk of PyQT/PySide, I can deal.

Those errors are always related with a bad implementation where there is something holding a reference to the qt python object represented by the bidding therefore keeping it alive even when their c++ instance has been already deleted. The solution is to go back to the drawing board and improve the implementation :)

Re: Hello Qt for Python

#172

Post by ptx »

always_good wrote: post #150
ptx wrote: post #142

Earlier quoted context omitted.

We have asyncio now to handle things in a non-blocking way with async/await. Someone just needs to write an implementation of asyncio.AbstractEventLoop that hooks into the Qt event loop.

And then they need to write an async version of everything you might want to use. And then they're done!

No, async versions of everything are already being written, based on asyncio. You just need the glue for using it with Qt.

Re: Hello Qt for Python

#173

Post by TimJYoung »

drb91 wrote: post #163
TimJYoung wrote: post #161

Earlier quoted context omitted.

Delphi's UI designer pioneered two-way tools, meaning that any changes to the contents of a form/window are reflected immediately in code. The general design is this: there's a code unit (.pas) and declarative UI property file (.dfm) for every form in your application. When you modify any published properties for any controls/components on the form via the object inspector, these modifications are stored in the .dfm…

Well hey now, python is strongly typed. Type declarations are just optional. :) just giving you grief. That said, especially the custom property editors would make e.g. Xcode’s interface builder almost worth looking at. I’ve just given up on graphical designers at all—last I checked thy were all terrible with responsive design, which is ironic on an ide that claims to target a mobile platform.

:-) Yeah, you're correct, I should have written statically-typed, not strongly-typed.

As for responsive design in graphical editors: what part do you find that they are terrible at, or is it that they don't do it at all ? Our previously-mentioned Elevate Web Builder will allow the developer to design responsive layouts that flow and move as you resize the container in the designer so that you can see how the design will behave at run-time.

Re: Hello Qt for Python

#176

Post by ris »

e12e wrote: post #147
ris wrote: post #144

Earlier quoted context omitted.

pip installing binary dependencies! What could go wrong?

With the new binary wheels, this actually works now - at least on Windows 10 and misc Linux distros (and according to other comments here, on Mac OS too). On Linux you might want to get the distros qt/qt-dev packages, as usual. But as far as I can recall, you generally don't have to.

Great - installing random (huge) binaries that have been compiled god-knows-how by god-knows-whom expecting god-knows-what other libraries to be on the target system.
Post reply on HN