141–150 of 166 posts
Earlier quoted context omitted.
What do you mean by the ecosystem?
The available libraries. For Python/JS, I can find libraries to do basically anything I want, but not so for Lazarus libraries.
That's really neat. It reminds me of generating a CLI based on docstring, which is another pattern that I like a lot.
Earlier quoted context omitted.
Delphi wasn't like that. There'a a gap a mile wide between 1) tools like Delphi, VisualBasic (the classic version, not .net), and to some extent, HyperCard 2) GUI builders, which were popularized by Visual C++ #1 doesn't have (visible) layers or abstractions. It's a different way to represent your program. You place a few controls, tie them to actions (code), and that's your system. #2 is like onions, with lots of me…
There is one GUI builder in Java I forgot the name, a plugin for Eclipse from Google, that allows to build GUI by drag and drop and jump into the code. It works directly by reading and writing any java code file, there are no extra files and layers of abstraction. It could understand Swing, SWT and a couple other major UI frameworks. That's the only thing I know that's really seamless like old times.
Earlier quoted context omitted.
Why not? I mean, it shouldn’t be _the_ deciding factor but it certainly should contribute greatly to the decision. Tools get popular for a reason. You get community support and a test-of-time guarantee that whatever you invest in today is more likely to last compared to the niche choice.
> "Tools get popular for a reason" Sometimes/often for completely wrong reason. And even if the reason was good in particular context then suddenly the tool gets dragged to be used well beyond the original intent.
>>> from guietta import _, Gui, Quit I am not looking forward to taking over projects using that framework abusing underscore and double underscore magic variables. The underscore "_" is a pseudo reserved variable in python. It is used in assignments like year,month,_ = readdate() to discard the return value and disable the lint warning about it.
Guietta looks interesting, but at a certain point if you're going to go with a visual representation of your gui to automatically generate it, you might as well go the whole docopt-style way and just have the whole gui defined in a docstring. That give you flexibility to have your own DSL as well (or jinja2 templates, or whatever), if you so decide, instead of needing to shoehorn python lists into the job. Plus that way you could actually modify the layout spacing, without much increase in complexity.
That being said, my usual recommendation for "I need a simple python GUI" is Toga [3]. The only downside is that Windows support is lagging behind MacOS and Linux, but it's not that far behind, so for simple stuff that should be reasonably acceptable.
[1] https://stackoverflow.com/questions/5893163/what-is-the-purp...
Every time I see something like this I think back to the glorious days of Borland Delphi with it's beautiful drag&drop GUI builder.
And WinForms/Visual Basic There was just something so natural about the way you could quickly throw together a UI and then hook everything up to it.
* What's the tab order? (Usually whatever order they happened to be created in, which is often wrong after the UI has gone through some changes.)
* Are they really exactly the same size or only almost the same?
* How do they behave when the window is resized?
* Does one button have one of its many properties set slightly differently from the other one? (Have fun inspecting them all and make sure to not accidentally change anything while doing so.)
* Did you just accidentally move one of the buttons one pixel while inspecting things?
I prefer doing the UI in code, so that everything is clearly spelled out and not hidden in some properties panel. In WinForms it works pretty well with TableLayoutPanel.
Petzold wrote about this approach: http://charlespetzold.com/etc/DoesVisualStudioRotTheMind.htm...
Every time I see something like this I think back to the glorious days of Borland Delphi with it's beautiful drag&drop GUI builder.
Earlier quoted context omitted.
Yes, I was inspired by PySimpleGUI (and say as much in the introduction: https://guietta.readthedocs.io/en/latest/intro.html ). But I felt that PySimpleGUI did not go far enough in making things simple. It also supports multiple backends, so that may be a reason to keep things more structured. Guietta is just a thin wrapper over QT.
> Guietta is just a thin wrapper over QT. So, any pro'n'cons in comparison to PyQt?
All in all, it's a wrapper that hides complexity and flexibility from you. Might be what you need some times.
Earlier quoted context omitted.
In my other life I used to manage bunch of developers while still developing myself. My criteria for hiring them generally was not their proficiency in particular tool but ability to grasp programming concepts in general and ability to grok any particular tool in short time. Practical experience in particular areas of course was a big plus. Over the time this strategy proved beneficial. My team ended up having the hi…
>My criteria for hiring them generally was not their proficiency in particular tool but ability to grasp programming concepts in general and ability to grok any particular tool in short time. I'm curious how did you test candidates for this? Did you give them any specific tasks to accomplish and then evaluate their ability to learn?
Earlier quoted context omitted.
> "Tools get popular for a reason" Sometimes/often for completely wrong reason. And even if the reason was good in particular context then suddenly the tool gets dragged to be used well beyond the original intent.
I like how you've nominated your own opinion as being the right reason, and everyone that made the tool popular as having the wrong opinion.