Build a media converter with Python, Qt and FFmpeg
|
|
|
Comments (8)
> It assumes things it aught not assume,
Much like most articles and posts assume readers know what arcane terms are being flung around with reckless abandon. I like to think I know what most linux topics are about, but I'm completely in a fog when I start reading up on this UEFI thing. Terms like "kexec", "PE binaries", "X.509". Geez, I spend more time reading wiki than the original article.
Also, we assumed you knew how to post to this forum. ;)
Much like most articles and posts assume readers know what arcane terms are being flung around with reckless abandon. I like to think I know what most linux topics are about, but I'm completely in a fog when I start reading up on this UEFI thing. Terms like "kexec", "PE binaries", "X.509". Geez, I spend more time reading wiki than the original article.
Also, we assumed you knew how to post to this forum. ;)
This is why whenever I start a tutorial series I start by clearly defining what I expect my target audience to already understand. That way when someone is confused on a topic they should have learned elsewhere I can just point them to those resources.
~Jeff
~Jeff
Jeff, that's always the right approach. I've also learned from experience that writing Linux articles is a no win experience. If you write them at a basic level the advanced users complain you are assuming they are idiots. If you write them at a more advanced level they are incomprehensible. Oh, and don't even get me started on writing reviews...
@Caitlyn - this is why I write articles that please myself.
Screw everyone else ;)
~Jeff
Screw everyone else ;)
~Jeff
After spending more time with that tutorial, I discovered it it not only incomplete, but it also contains significant errors. The code, as presented, simple will not and cannot work.
As a tutorial it is useless, as an introduction to Python it is useless. Anyone who has not Programmed in Python will gain no insights into Programming with Python, as the code, as presented will never work. And rather than demonstrating how easy it is to create a small application using Python and Qt Creator, it delivers the exact opposite.
The article should have been titled "How to confuse and turn people away from Python."
As a tutorial it is useless, as an introduction to Python it is useless. Anyone who has not Programmed in Python will gain no insights into Programming with Python, as the code, as presented will never work. And rather than demonstrating how easy it is to create a small application using Python and Qt Creator, it delivers the exact opposite.
The article should have been titled "How to confuse and turn people away from Python."
Quoting:The article should have been titled "How to confuse and turn people away from Python."I'd bet I could write that article with that title and succeed. My Python coding definitely needs help.
So does mine, and what my coding particularly needs is help in understanding event handling models in QT and GTK, the event handling models I'm used to seem quite different from the concept of Slots and Signals.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

It assumes things it aught not assume,
the code mentions a path that simply doesn't exist on my Debian lineaged system
#!/usr/bin/env python3
the code itself throws errors, that clearly are not expected by the writer, at the most basic level for example
Traceback (most recent call last):
File "main.py", line 2, in <module>
from PyQt4 import QtCore, QtGui
ImportError: No module named PyQt4
even though all those libraries are actually installed.
It assumes the student knows where the following code can be found, or needs to be written
I didn't get past this point as this was a blocking error.