I’ve always thought there’s so much low hanging fruit in making simple interfaces easy to make.
We’ve lost so much ground since vb6.
Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
11–20 of 38 posts
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#12I’ve always thought there’s so much low hanging fruit in making simple interfaces easy to make. We’ve lost so much ground since vb6.
Youll be happy to hear Delphi is still alive and well, thanks to Embarcadero
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#13Our company made the switch to QT, dev time and code readability has improved, but the code runs significantly slower in debug mode. (Yes I know we can run headless) Sad because I learned so much tkinter, and despite that, I'm fine with moving away from tkinter. I'm not sure who the problem is.
Have you tried QML? My efficiency improved dramatically since switching from C++ Qt for the UI.
Do you have to pay to license QML?
Qt looks nice but license fees are pretty expensive for small shops.
Could use the GPL version but I’m just afraid of becoming dependent on a tool that will keep the most interesting features only available for the commercial version.
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#14I’ve always thought there’s so much low hanging fruit in making simple interfaces easy to make. We’ve lost so much ground since vb6.
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#15I’ve always thought there’s so much low hanging fruit in making simple interfaces easy to make. We’ve lost so much ground since vb6.
Youll be happy to hear Delphi is still alive and well, thanks to Embarcadero
More like in spite of Embarcadero...
There's still Lazarus[1], and Common Lisp got CLOG [2] which is very much like Delphi except in the web and in Lisp
[1] https://www.lazarus-ide.org/ [2] https://github.com/rabbibotton/clog
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#16It would be exciting to see future iterations of this tool incorporate native OS styling or even output to other GUI frameworks like QT or Toga.
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#17Earlier quoted context omitted.
Have you tried QML? My efficiency improved dramatically since switching from C++ Qt for the UI.
Do you have to pay to license QML? Qt looks nice but license fees are pretty expensive for small shops. Could use the GPL version but I’m just afraid of becoming dependent on a tool that will keep the most interesting features only available for the commercial version.
We use GPL version, but its internal software that isnt distributed outside.
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#18It would be exciting to see future iterations of this tool incorporate native OS styling or even output to other GUI frameworks like QT or Toga.
Haven’t tried but I think Qt Designer has already integration with Figma
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#19Earlier quoted context omitted.
How do you maintain the generated code? Once you make changes to it, you can't regenerate it without losing the changes.
I just use it to create the initial layout and then if I need anything additional I just ask chatgpt to create it. You still have to know what you’re doing but I find that GUI code is mostly boilerplate code that is really tedious to create from scratch. ChatGPT is a 5x productivity boost.
How do you describe the overall layout to Chatgpt? individual components sounds simple.
Re: Tkinter Designer: Quickly Turn Figma Design to Python Tkinter GUI
#20Earlier quoted context omitted.
Have you tried QML? My efficiency improved dramatically since switching from C++ Qt for the UI.
Do you have to pay to license QML? Qt looks nice but license fees are pretty expensive for small shops. Could use the GPL version but I’m just afraid of becoming dependent on a tool that will keep the most interesting features only available for the commercial version.
Not at all! Qt comes with an LGPL version that you just must 1. link it dynamically and 2. If you change Qt's source code you need to publish the changes. (Not legal advice).
Most of what you'll need will be under the LGPL version. You can use the commercial version by paying and not publishing your source or via the GPL license and publish your full source code and everything else GPL requires.
I cannot recommend it more, give it a try it's easy to learn (I studied the basics in a day and a working prototype quite fast).
Something I've been working on: converting Markdown text into a Kanban view (in QML).[1]