I’m sitting at work (Starbucks) typing up a random blog entry to get back into the habit of the blogging phenomenon. I couldn’t tolerate the old four sidebar style, so I’ve changed the blog appearance. Development on KyUI is halted temporarily while I teach myself QtNetwork. I’ve got two new widgets to throw into the mix, one based on work from another PyQt programmer. I’ll talk about that once it’s presentable. There are other ideas churning, but I’d rather not get into them until I actually make…what’s the word?…progress.
Working with QNetworkAccessManager is interesting. I converted the PyQt-converted-from-Qt example for QHttp to QNetworkAccessManager, and the results were less than inspiring. QNAM (as I’ll abbreviate it) decided my Internet access was unavailable with a decidedly confusingly generic error message. I’m writing a tidbit of software that reads in HTML, grabs information out of it, and generates the appropriate link to a wallpaper JPEG without running through intermediary HTML. It’s teaching me QtNetwork and managing lots of signals and possible error conditions. I have to admit that–after some heavy cursing–QNetworkAccessManager is better than QHttp, particarly with the use of QNetworkReply as a QIODevice. The one feature of QHttp that I miss is using QNetworkAccessManager.get() to funnel a request directly into a QIODevice, specifically a file. Yes, QNetworkReply is an io buffer, but it would be nice if I could call get(QNetworkRequest, QFile) and wait for the finished() signal from the QNetworkReply it returns without waiting for the readyRead() signal and chunking data into the file. Just a thought.
Other thoughts: contentsMargins should be a QProperty for QWidget and QLayout. I use keyword arguments almost exclusively to set initial QObject subclass states, and not being able to set the contents margins this way is irritating.
I’m off now…into The Cloud.