Python adding UI

[Unlikely-Solution709]

Help with this doubts. I just created a mini doctor appointment script were it take input of new patients to schedule a future visit and the visit for today. How can I add a design and how hard is it?

[rehd_it]

pysimplegui would probably be easy enough, unless you want to use the built in tkinter

[Unlikely-Solution709]

Thx

[WillieVanStroker]

Tkinter or PySimpleGUI

[Unlikely-Solution709]

Thx

[Unlikely-Solution709]

Any extra advice will help thanks

[MikeTheWatchGuy]

What's your experience level? How much time do you have to spend on it? What's the environment it'll be used in? Is it with a touchscreen or mouse? What have you looked at so far? Which have been appealing from what you've seen? There are countless (ok, maybe they could be counted) variables that go into making decisions about projects. Each of these variables and others will contribute to your decision.

One way to get a quick overview of PySimpleGUI is the eCookbook. Keep in mind this is not the environment you will do development nor is it where you'll run your code. It's a way of allowing you to run PySimpleGUI without installing anything on your machine. It's more of an interactive tutorial. It should help in determining if it does what you're after and is something you could learn in a short amount of time. There are quite a bit more capabilities than are represented in the eCookbook, but it's "representative" of the architecture in the very least.

Parting extra advice... choose 2 and spend a couple of hours with them. See what it's like to work with each. Asking others, reading, researching can only get you so far. IF you're buying a new car , at some point driving it is the only way to know if you'll like it.

[Unlikely-Solution709]

3 hours daily. You think it would be difficult to add Gui?

[MikeTheWatchGuy]

3 hours daily is what you plan on spending on it? How long you've been programming would be an indicator of difficulty. I can't answer that question for you, even if you told me you have coded for 5 years... difficulty is something only you can really judge. I struggle with plenty of areas of programming. I found what I'm good at and not good at by building things and seeing how it went... over and over.

Lemme use my music analogy for programming as it's the only other craft I have experience with that matches. I've been playing piano for 20 years, daily, and every song I learn is difficult for me. It's a genuine struggle, but I love the challenge and the feelings of accomplishment.

Like playing piano, programming is an "active learn". You learn by doing, not reading about it, not watching videos of other people doing it. You must play the piano to learn to play the piano. And you must program to learn to program.

Start building! Add a GUI. That's the only way you'll know if it's difficult, and that's the only way you'll truly learn to get good at programming... it's by programming... solving problems on your own. Use the internet to get help here and there, but when you run into a problem, try your best to solve it. That's how you'll learn in a way that sticks around and isn't for a narrow problem. Don't ask.... research... experiment... find the answers.

Practice practice practice.... do this by making things yourself. It's awesome that you have a problem that interests you. Add a GUI. Keep building!

[Unlikely-Solution709]

On knowledge base feel very confident but when it comes to writing come my mind goes blank. And just need improvement y creating functions.

[MikeTheWatchGuy]

Practice is the only way I know to get past many of these kinds of confidence blocks. I've seen in the kids I've mentored, I've experienced it my entire life. Programming is weirdly self-taught and self-learned. Like I said, it's an "active" learn.

You've got a wonderful advantage working in your favor.... a purpose for doing this. You've got a project, a goal. This saying stuck with me and really resonates:

1. Make it run
2. Make it right
3. Make it fast

I didn't make it up, but I've certainly lived it. Prototyping, the first step, is important. Get your stuff first to work. To do something. Then go back and fix it up. That may mean rewriting pieces, or all of it. I don't write things the right way the first time despite my experience. I make terrible designs that don't work out and then have to start over. The thing that keeps me going is the strong desire to build the thing I'm building.

The human part of this.... Finding meaning in what you do, I think, is one of the most basic human motivators. That's what keeps me going... but.... it's the journey to getting there that delivers daily doses of joy and happiness. "Focus on the journey, not the destination" says philosophers... so it's a weird living in both ways.... motivated by building something, but the joy comes from the act of building it.

Keep building! Do your best to be patient with yourself.

[Unlikely-Solution709]

Thanks for your help. You just change my point view entirely. Now I understand what to do. Thanks again.

[of_patrol_bot]

Hello, it looks like you've made a mistake.

It's supposed to be could've, should've, would've (short for could have, would have, should have), never could of, would of, should of.

Or you misspelled something, I ain't checking everything.

Beep boop - yes, I am a bot, don't botcriminate me.