>> Next, your suggestions are exactly what I was looking for. The following
>> prototype is showing what am I after (ugly, no classes, but take it as a
>> prototype):
> .
> .
> .
> We're not saying that good Python code must be expressed
> with classes, are we?
No, we aren't. In fact, in many of my real-life applications I'm using
procedural or
functional code, according to what I feel suits better the given situation.
Moreover,
when I wrote "ugly", I wasn't meaning "classless", but rather using "r" instead
of "root",
"st" instead of "style", "a=b" instead of "a = b" and so on. "no classes" is
just a
reference to the traditional (and rationally justified) use of classes in a GUI
context.
I hope this clarifies things out :-)
SxN
__________________________________________________________________
Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your
favourite sites. Download it now
http://ca.toolbar.yahoo.com.
_______________________________________________
Tkinter-discuss mailing list
[email protected]
http://mail.python.org/mailman/listinfo/tkinter-discuss
