4 ms·

I found it delightful and appreciate the lengths the author went in explaining why this exists and the goals of the project. A breath of fresh air compared to t

by tjpnz 3y ago

I found it delightful and appreciate the lengths the author went in explaining why this exists and the goals of the project. A breath of fresh air compared to the usual sea of boilerplate and links to proprietary chat apps I don't want to use.

lionkor 3y ago
I urge you to scroll to any point in the readme and read, and recount what you read, because most of it is repetetive and fluff for no (obvious to me) reason
- makeitshine 3y ago
  Seems fine to me. In fact, it seems way better than most docs. I don't get the issue you're having with this.
bmitc 3y ago
There is a lot of non-information, for sure. For example, > Some programs are not well-suited for PySimpleGUI however. By definition, PySimpleGUI implements a subset of the underlying GUI frameworks' capabilities. It's difficult to define exactly which programs are well suited for PySimpleGUI and which are not. It depends on the details of your program. Duplicating Excel in every detail is an example of something not well suited for PySimpleGUI. says absolutely nothing and gives the reader no useful leads as to the applicability of the framework to their project.
- aebtebeten 3y ago
  That's the key part of the entire README; I found it very well put. tl;dr: "you will be disappointed if you want to do something fancy" (of course, should you want all three of (a) easy, (b) fancy, and (c) someone else has already done much of it for you, I'd bet you would be bound for disappointment anyway)
  - bmitc 3y ago
    It would be the key part if it had actual information. What type of programs are "some programs"? Too many controls, multi-window, drag-and-drop, too fast control updates or rendering, 2D graphics, extensible controls, etc.? GUI frameworks have pretty common components, and clearly they know something about the limitations, but those limitations aren't enumerated at all.
    - 082349872349872 3y ago
      Compare it to a house listed at "price upon request"? As JP Morgan said, if you have to ask...

by tjpnz 3y ago

lionkor 3y ago

I urge you to scroll to any point in the readme and read, and recount what you read, because most of it is repetetive and fluff for no (obvious to me) reason

makeitshine 3y ago
Seems fine to me. In fact, it seems way better than most docs. I don't get the issue you're having with this.

bmitc 3y ago

There is a lot of non-information, for sure. For example, > Some programs are not well-suited for PySimpleGUI however. By definition, PySimpleGUI implements a subset of the underlying GUI frameworks' capabilities. It's difficult to define exactly which programs are well suited for PySimpleGUI and which are not. It depends on the details of your program. Duplicating Excel in every detail is an example of something not well suited for PySimpleGUI. says absolutely nothing and gives the reader no useful leads as to the applicability of the framework to their project.

aebtebeten 3y ago
That's the key part of the entire README; I found it very well put. tl;dr: "you will be disappointed if you want to do something fancy" (of course, should you want all three of (a) easy, (b) fancy, and (c) someone else has already done much of it for you, I'd bet you would be bound for disappointment anyway)
- bmitc 3y ago
  It would be the key part if it had actual information. What type of programs are "some programs"? Too many controls, multi-window, drag-and-drop, too fast control updates or rendering, 2D graphics, extensible controls, etc.? GUI frameworks have pretty common components, and clearly they know something about the limitations, but those limitations aren't enumerated at all.
  - 082349872349872 3y ago
    Compare it to a house listed at "price upon request"? As JP Morgan said, if you have to ask...