To save people the time of not having to read it all to know how to do something so simple as to install it when it could just be made to install itself?

I can insult you, but you can’t call me out because I’ll insult you again. lulz!!

The code is open and there for you to read. What you’re actually saying is you’re too lazy to read and understand it because the world owes you something. amirite?

Arch users don’t value their time.

Having a “great” understanding of how a Linux system is tied together is fine for the now, but in five years time, will be useless as things change so why not spend your time being productive in the now.

mentioning pointers, time sharing, endianess, word size, registers

You’re making me hard! Don’t stop!

It actually leads to a fantastic product and more free time because you’re not having to babysit kids who think the world owes them something because they can code ‘hello world’ in python.

Oh the irony. What’s gatekeeping about not wanting rubbish code in your repository? Lack of knowledge is self-gatekeeping.

The ‘wah wah…boomer’ cries are…cringe. Either step up with the knowledge and action, or don’t bother and cry “gatekeeping”.

And this is how I see Linux quickly unravelling and planned insecurities creeping in over the next decade or so.

I do miss the tags of SVN that would replace certain strings on each commit such as the date, a version number, etc.

All of javascript is kinda just pretend.

CVS is gonna make a comeback! I tell ya!

In the case of this gist, it’s premature optimization. Generally it’s necessary cuz new implementations come along often.

That sounds terribly inexperienced. That’s exactly what updates to code are for. You cannot manage all kind of, sort of similar but different libraries with one code base. It would be horrific to even consider it.

By embedding the class, creates a limitation that prevents abstractions or other implementations of each component. Imagine every suggestion in this conversation thread is another variation with a separate implementation.

If the user wanted to create a new FoldableDockWidget with a different title bar, they’d extend the FoldableDockWidget class and override the Titlebar method in their extension of it. I understand your point, but isn’t it over optimisation?

The widget class belongs to the FoldableDockWidget class until it doesn’t. Then a refactor is needed.

One line of instantiating code. I can’t imagine where or how the custom title bar would be used outside of the Foldable Dock Widget class though. That’s probably the real reason why I made it a sub class. Not how I’d do it in other languages, but in Python? I’m trying it out!

Hardwiring a particular implementation of the Windowing python wrapper is necessary. They have slightly different implementations. If something magically new comes along, then, the code is updated. Again, over optimisation here which is unnecessary.

The code in the process guard is just sample code to demonstrate use of the class. No big deal. It’s separate to the class and not to be imported because… this is a gist of sample code!

Thanks for the compliment! Python isn’t my first language and it’s difficult to be able to switch style from one language to another!

I always find it difficult to choose when to use ternary statements. Sometimes, for something quick and simple, I will, otherwise I’ll be explicit. This is more of a readability issue than anything else. And I find the ternary statements quite verbose compared to other languages by using the words if/else rather than shorthand symbols.

You’re absolutely right about the set_float_icon and corresponding method. Coding’s an iterative process and that’s a byproduct. I think set_float_icon() along with complimentary methods like set_docked_icon(), set_minimize_icon(), set_restore_icon() etc may be easier to use / remember wtf it does in six months time!

Thanks for the black / ruff suggestion. I’ve never heard fo them, but I’m about to go look for them.

Thanks for your response.

should never embed classes within other classes)

Why is this? I have to admit that coming from other languages, it feels dirty, but is there a pythonic good reason for this? The class ‘belongs’ to the FoldableDockWidget class, so I figure it’s the best place to put it.

Thanks. I wondered why I instinctively text-transformed the title of the widget to uppercase! I commented it out thinking perhaps it doesn’t look grammatically correct! Reduced the font size a bit and I think it looks a heck of a lot better now!

Qt automatically handles the conversion of QDockWidgets into tabbed docked widgets when one is dragged over an existing one.

I have a little demo video, but I have no idea where to upload it to!

what’s “large” and what’s “cheap”?

If you’re going to print something, just buy a book. It’s much cheaper and you don’t have to deal with the carcinogenic effects from the printing.

Online guides are often poorly written.

What do you use Wayland for? Gaming?