[Tkinter-discuss] tcl/tk's syntax to python's syntax

adil gourinda rikudou__sennin at live.com
Tue Oct 31 07:59:00 EDT 2017

Tkinter is the standard GUI for python but there is no official Tkinter's documentation so I am obliged to read from Tcl/Tk reference ( http:// tmml.sourceforge.net<http://tmml.sourceforge.net> /doc/ tk / index.html<http://index.html>), To make Tcl/Tk syntax EASY TO READ for pythonic programmers I made those diagrams, My purpose is so simple.
From: Tkinter-discuss <tkinter-discuss-bounces+rikudou__sennin=live.com at python.org> on behalf of Rob Ward <rl.ward at bigpond.com>
Sent: Monday, October 30, 2017 3:35:45 AM
To: tkinter-discuss at python.org
Subject: Re: [Tkinter-discuss] tcl/tk's syntax to python's syntax

Unfortunately I am not an expert, so my feed back is extremely limited, however I can see value in what you are doing. I have been designing a simple PCB designer to drive my CNC machine. It is Python 3 and uses the tkinter library. I am making good progress but find the syntax for the GUI elements somewhat "taxing" as it makes the setting up the components feel like a dog's dinner. Different, but related functions, don't feel logical. Given the amount required for even a simple GUI any rationalisation of the syntax that helps understand their interdependence would be good. I hope I have understood your intentions.
Cheers, RobW

On 27 October 2017 8:24:41 pm AEDT, adil gourinda <rikudou__sennin at outlook.com> wrote:
I am asking your opinion about the last diagram, I want to solve the pathname problem with it.
From: Tkinter-discuss <tkinter-discuss-bounces+rikudou__sennin=live.com at python.org> on behalf of Michael Lange <klappnase at web.de>
Sent: Monday, October 23, 2017 10:27:19 AM
To: tkinter-discuss at python.org
Subject: Re: [Tkinter-discuss] tcl/tk's syntax to python's syntax


On Sun, 22 Oct 2017 21:11:48 +0000
adil gourinda <rikudou__sennin at live.com> wrote:

> With the aim to make translation of tcl/tk's syntax to python's syntax
> more easy I made this flowchart and I ask you to check it.
> Thanks for your help😊

I think the translation of the Tk pathName is problematic. One thing that
might come closer could be

        ".parentWidget.childWidget" -> "Instance"
        ".parentWidget" -> "parentWidget"

But strictly speaking I think this is not correct either. If the Tk root
window is the parent, parentWidget is only "." . If a Frame ".f" is the
parent, parent widget *is* ".f" in Tk,and a Button widget "b" that is a
child of ".f" in Tk *is* ".f.b". Of course considering this the chart
might look a bit pointless, like

        "parentWidget" -> "parentWidget"

Actually the widgets' names (as "b" and "f" in the above example) go to
the widget's "name" option in Python, which is hardly ever used though
(in Tkinter we usually let Python assign the widget names automatically
which leads to something that looks like ".1234567890.1234567891" instead
of ".f.b").

I hope this makes some sense, and maybe one of the Tk experts here can
provide a better explanation.

Best regards


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It [being a Vulcan] means to adopt a philosophy, a way of life which is
logical and beneficial.  We cannot disregard that philosophy merely for
personal gain, no matter how important that gain might be.
                -- Spock, "Journey to Babel", stardate 3842.4
Tkinter-discuss mailing list
Tkinter-discuss at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tkinter-discuss/attachments/20171031/79a263a2/attachment.html>

More information about the Tkinter-discuss mailing list