[1] https://www.effbot.org/zone/element-tkinter.htm
[2] https://github.com/calroc/pygoo
[3] http://pages.cpsc.ucalgary.ca/~aycock/spark/ "Scanning, Parsing, and Rewriting Kit"
121–130 of 166 posts
[1] https://www.effbot.org/zone/element-tkinter.htm
[2] https://github.com/calroc/pygoo
[3] http://pages.cpsc.ucalgary.ca/~aycock/spark/ "Scanning, Parsing, and Rewriting Kit"
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.
I personally think the real reason those types of tools seem less common and popular today is that people remember for example the reputation that Visual Basic programmers got (by the way, I was one). Basically, any really convenient RAD/GUI tool has an association with beginner programmers or even users. The last thing programmers want to be identified with is a user. Programming is manipulating cryptic colorful tex…
I believe that reframing the matter in terms of user empowerment might be the way forward. To create tools that help casual users accomplish tasks they might otherwise have needed a programmer for is to empower users. Excel is a classic example of user empowering software, as it allows people with the self-image of "user, not programmer" to effectively write programs, even if they may not recognize it as such. I thin…
Slightly off topic: Does somebody have a recommendation of a toolkit or library for simple data entry and display with Python? Basically I want to replace Excel/Calc for mostly tabular data, because I hate the programming and data access model (e.g. instead of writing B$8 or sum(A9:A23) I would like to have map/reduce function with reasonable variable names). But the presentation and entry speed is much better with s…
Earlier quoted context omitted.
You don't even have to go back that far. XAML and C# developed with Visual Studio and Expression Blend is a fantastic experience, it almost makes me wish Silverlight was still around.
It's much heavier than what we had with Delphi/VB, it feels like wading through treacle in comparison.
In fairness, I haven't done any Windows desktop development for some time, so the XAML designer might be less crap nowadays.
Earlier quoted context omitted.
Actually I started to develop Guietta exactly because using the QT GUI builder (Qt designer) was often too time consuming for simple applications. Designer works great for GUIs with complex layouts. Having an intermediate XML representation puts a lot of distance between your code and your GUI. Sometimes this is good, other times is not. I rant a bit about this at the start of the introduction: https://guietta.readth…
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…
That's the only thing I know that's really seamless like old times.
Earlier quoted context omitted.
I believe that reframing the matter in terms of user empowerment might be the way forward. To create tools that help casual users accomplish tasks they might otherwise have needed a programmer for is to empower users. Excel is a classic example of user empowering software, as it allows people with the self-image of "user, not programmer" to effectively write programs, even if they may not recognize it as such. I thin…
I sell sharp knives as "surgeon empowerment" devices. Anyone can surg!
Analogously, the tools already available to computer users are tools that could harm the user if used improperly. To not empower users because they might harm themselves isn't progressive, it's paternalistic.
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…
It's been a while (I've never done autolayout and up) but I found Xcode Interface Builder to work in the fashion you describe. Probably not an accident as it descends from NeXT devtools which inspired e.g. VB (not sure about Delphi).