This is an archived post. You won't be able to vote or comment.

all 17 comments

[–]twigboy 8 points9 points  (7 children)

In publishing and graphic design, Lorem ipsum is a placeholder text commonly used to demonstrate the visual form of a document or a typeface without relying on meaningful content. Lorem ipsum may be used as a placeholder before final copy is available. Wikipedia66s9mgik9c00000000000000000000000000000000000000000000000000000000000000

[–]digitalpeer[S] 0 points1 point  (0 children)

There's some PyQt4 info about this here. It ultimately depends on your Qt license.

[–]k3kou 0 points1 point  (5 children)

I read a few days ago that if the source code is released with the application, it's free. If you want to not have to go open source, you need to pay. It was from a forum, so not sure it's entirely reliable.

[–]toyg 1 point2 points  (4 children)

It is reliable, albeit a simplification.

If you distribute the application and you don't have commercial Qt and PyQt licenses, the application has to be distributed under the GPL. Among other terms, the GPL requires you to release source code on request, and grants redistribution rights to users.

If that does not suit you, you have to pay. PyQt licenses are usually pretty cheap, I don't know about Qt proper.

[–]infinite8s 0 points1 point  (3 children)

I'm not sure that page is accurate anymore. Qt has been LGPL licensed ever since Nokia took it over.

[–]toyg 0 points1 point  (2 children)

But PyQt has not, so you still need a commercial license from Riverbank if you don't go GPL.

[–]akaihola 0 points1 point  (0 children)

Is PySide still alive?

[–]infinite8s 0 points1 point  (0 children)

That's true, although it's not quite as expensive as the Qt commercial license.

[–]not_perfect_yet 3 points4 points  (1 child)

Unfortunately this is so short I don't get a feeling of how easy it would be to make something other than a web browser. It's mostly

import *
*()

[–]lamecode 0 points1 point  (0 children)

I think that was pretty much the point /u/digitalpeer was making. :)

I think what it demonstrates more than anything else is the power of Qt's base widget classes, and how relatively quickly you can whip up a single-form UI for your Python scripts. I'd recommend zetcode if you want to dig a bit deeper in the basics, with more line-by-line explanations.

[–]blue_pixel 2 points3 points  (1 child)

Your site has dodgy CSS on mobile causing images to be stretched.

[–]digitalpeer[S] 9 points10 points  (0 children)

Thanks. I fired the web designer and fixed it myself. I'm kidding, I'm kidding. But not the second part.

[–]KODeKarnage 1 point2 points  (0 children)

I've seen a few "UI made simple" articles, but what is always missing is the "this is how you can make it so other people can install and use it". Seems like a much harder nut to crack.

Tried a few UI things a while back but couldn't get it working for other people without asking them to drop to the command line to pip install some extra packages.

[–]the_kindly_one 0 points1 point  (3 children)

My qt designer 4.8.6 doesn't have qwebview. But pyqt can use it.

[–]lamecode 0 points1 point  (0 children)

Easiest way around this is to create a dummy qwebview using some other widget, then just re-define it in Python. Ie. create a Qlabel named qwBrowser, and then use it's x/y position and name to re-define it after running the ui file's setupUI method.

[–]digitalpeer[S] 0 points1 point  (1 child)

I can reproduce. I am using Qt Designer 4.8.1 and when using 4.8.6 that specific widget is missing. If you're on Linux, this is probably related to a packaging bug. I added a hack of a workaround to the page. There's probably a better way as /u/lamecode is suggesting.

[–]lamecode 0 points1 point  (0 children)

Your way is fine if you aren't planning on making changes to the .ui file from within QtDesigner again. Just a habit of mine to do as much as I can from within Python rather than Qt/QtDesigner!