wxPython

What is up, and welcome to yet another awesome tutorial series.

This series is going to be covering WXPython.

So, what is WXPython? WXPython is a cross-platform toolkit used for making GUIs, or graphical user interfaces.

This is done so the end user doesn't actually have to communicate with the Python interpreter window, right? So nobody wants to develop programs and have to deal with this, or a DOS prompt.

It's just a plain, more user-friendly way to make programs and have users use those programs.

WXPython itself is actually just kind of like a wrapper around the language C++.

Now, what that means is WXPython itself is not actually coded directly in Python.

Instead, it's more of like a Python interpreter, kind of like you have a Python interpreter that you installed on your system because your computer didn't naturally understand Python.

Hello and welcome to another WXPython tutorial.

In this tutorial we're going to be building off of the last WXPython tutorial.

And this is what we had last time.

We'll just run it real quick.

I could relatively easily...

It was written in wxPython, which meant that I could create an application that would support Mac or Windows or Linux, uh, with one set of code, and it was relatively easy to bind objects in and, and it all sort of worked okay.

So it wasn't too hard, and it, it reduced the friction for new users so they could get up-

Mm

We may have had developer skills, and we just didn't want to spend six months developing something because it's just slower, and I don't have – I'm just speaking for myself, right? I wouldn't have the bandwidth to take on – Opening up Visual Studio and opening up a new project and going from one line of code to an end product.

But what we're finding is that the frameworks that these tools are using, whether that be WXPython or, I mean, you name it.

That we're running into, and this is, by the way, not the fault of you at all, Vispero.

It is the fault of the frameworks because the frameworks are not giving us the information that we need.

Or if we contribute code, then they don't take the code.

I mean, you know, right? So, like, for example, check boxes and list views for WXPython.

really, really painful thing, right? In other words, there's no way for you to say, hey, you know, Claude, build me a WXPython app, you know, put a list view here, allow me to check off the items that I want and which ones I don't want so I can arrow up and down and tell me which ones are checked or not checked.

Yeah, it will do that, but it's not visually available because the information is not conveyed Technically, and we won't get into all of what that really means, all that minutia, but is this an area that – and I know that's kind of beyond your control and you kind of have to partner with people, but it's – I don't know.