ANN: Thinking in Tkinter

[Stephen Ferg]

Greg Ewing <see_reply_address at something.invalid> wrote in message news:<3D7FF299.2020509 at something.invalid>...
> It might be better to start with some object
> other than a button for the purpose of introducing the
> concepts of event binding. Otherwise you're teaching
> people an incorrect way of using buttons that they're
> going to have to unlearn later.

Thanks for your help in other messages in this thread.  

After thinking it over, my current plan is still to start with Button,
just because it supports both event binding and command binding.  And
also, of course, because Button is the obvious choice for the first
widget to learn.

So my plan now is first to explain event binding on Button.  Then I'll
explain command binding on button, and do a "compare and contrast"
with event binding:  discussing why command binding is better than
event binding, noting that it does NOT automatically pass an event
object, that it may be available with other widgets than Button, etc. 
And I'll be careful in the earlier discussion to note that even though
we're looking at event binding first as a way to introduce the concept
of binding, we'll also soon be looking at a better way (i.e. command
binding).