Live data from Hacker News

PysimpleGUI

github.com

1–10 of 159 posts

Re: PysimpleGUI

#2
Does anyone have experience with this? The goal to lower the entry bar for GUI development seems laudable to me, wonder where the solution stops to work, though.

Re: PysimpleGUI

#3
I have one comment, and I hope it's not rude: There is too much text. Everywhere where you can put text, the author put a lot of it. Sentence after sentence, rambling on. Coherently so, most of the time, sure, but just one after the other and not a single relevant screenshot for the first thousand words.

Something is not right here. Either this is a joung enthusiastic coder, which is probably the case, or there is so much text in order to convince you to try it.

The readme even has an about me section where the author introduces himself.

For some examples, scroll to random points in the readme and read a few paragraphs, then repeat what you just read.

Re: PysimpleGUI

#4
post #2

Does anyone have experience with this? The goal to lower the entry bar for GUI development seems laudable to me, wonder where the solution stops to work, though.

Not to answer your question but it brings back some nice memories. I was in college when author started this project. He worked a lot on it. After a few years, he stopped and archived the project. Looks like it's back again. Nice!

I used it in all my college demo and small projects and I loved it. The most complex GUI that I made was a oscilloscope frontend for lab-made signal recorder. It is indeed a simplegui library.

Re: PysimpleGUI

#5
post #3

I have one comment, and I hope it's not rude: There is too much text. Everywhere where you can put text, the author put a lot of it. Sentence after sentence, rambling on. Coherently so, most of the time, sure, but just one after the other and not a single relevant screenshot for the first thousand words. Something is not right here. Either this is a joung enthusiastic coder, which is probably the case, or there is so…

Lol. He is definitely not young as in inexperienced coder. He will definitely not going to win awards for barely sufficient documentation and docs organisation. Dude got a personality.

I've followed the project when I was in college and used it in my personal project.

Re: PysimpleGUI

#8
post #6

In 2023 isnt it almost always better to make a webapp through dash or something if you need a “gui”?

When the only tool you have is a hammer, everything is a nail.

It depends on your requirements. I still produce actual native GUIs for tools I write. They're faster, require less futzing to service, generally continue working for years if not decades, have far richer control possibilities out of the box and tend not to rely on 5000 layers of excrement slapped on top of each other.

Oh and no fucking Javascript!

Re: PysimpleGUI

#9
post #3

I have one comment, and I hope it's not rude: There is too much text. Everywhere where you can put text, the author put a lot of it. Sentence after sentence, rambling on. Coherently so, most of the time, sure, but just one after the other and not a single relevant screenshot for the first thousand words. Something is not right here. Either this is a joung enthusiastic coder, which is probably the case, or there is so…

I just scanned it. It's not an MVP for some product they want to attract investors. It's a tool. Which has documentation written by someone who wrote it.

I hope this one is not rude too: are you sure you're just not afraid of having to read stuff rather than being spoon fed bullet points and steps?

Re: PysimpleGUI

#10
Looks good. I have a suggestion for it, although it might be this library is too mature for such a dramatic change: use dictionaries (which, as of a recent Python, remember which order the elements were inserted) instead of lists.

I did something like that in an old job, except it was a much thinner wrapper around PyQt (and surprisingly little code). A key difference is that setting properties/signals and nesting widgets was done together. One benefit of that over setting properties in the constructor is that, if you need a name for a widget (e.g., to set the text later), you can still set the properties of it in the main bulk of the view.

    self.mytext = QTextEdit()
    view = {
        "title": "My Window Title",
        QVBoxLayout(): {
            self.mytext: {
                "text": "Initial text",
            },
            QPushButton(): {
                "text": "copy from self.mytext",
                "clicked": self.copy_text,
            }
        }
    }
    setup_view(self, view)
The "setup_view" function was the whole API. They talked about opening sourcing it as part of something else – I hope they do because I found it really handy for quickly knocking together simple GUIs. But this library looks like a good alternative, so thanks for posting.
Post reply on HN