On 1/24/11 11:58 AM, Octavian Rasnita wrote:
>> From: "Ethan Furman"
>> Please do not repost rr's crap in its entirety, or you'll find yourself
>> added to many killfiles -- just like he is.
> I am not posting anyone's crap. I just informed why Tkinter is bad.
> And I also don't say that WxPython
From: "Ethan Furman"
> Octavian Rasnita wrote:
>> From: "rantingrick"
>>> WxPython versus Tkinter (A code battle to the death!)
>>>
>>> by Rick Johnson.
> [...]
>
> Octavian,
>
> Please do not repost rr's crap in its entirety, or you'll find yourself
> added to many killfiles -- just like he i
Octavian Rasnita wrote:
From: "rantingrick"
WxPython versus Tkinter (A code battle to the death!)
by Rick Johnson.
[...]
Octavian,
Please do not repost rr's crap in its entirety, or you'll find yourself
added to many killfiles -- just like he is.
~Ethan~
--
http://mail.python.org/mailman
On 1/24/11 1:52 AM, Octavian Rasnita wrote:
Well, I have also tested the program dirbrowser.py, but it is not decent
at all.
I have tested it with JAWS screen reader and it is absolutely inaccessible.
The single "accessible" things in it are the title bar which is "tk".
It can't compare with t
From: "Kevin Walzer"
I found this code in the Demo/tkinter/ttk directory of the Python 2.7.1
source distribution. I'm NOT the author (credit should probably go to
Guilherme Polo, developer of the Tkinter wrapper for the ttk themed widgets
that is now in the stdlib). But, using a tree/listview
I found this code in the Demo/tkinter/ttk directory of the Python 2.7.1
source distribution. I'm NOT the author (credit should probably go to
Guilherme Polo, developer of the Tkinter wrapper for the ttk themed
widgets that is now in the stdlib). But, using a tree/listview widget
that is part of
rantingrick schrieb:
[snip]
1. You cannot define the terms--restrict your opponent--
and battle it yourselves.
2. Your specified directory browser is useless.
--At least define that the directory browser must have
constant complexity to work with volatile
data over a network...
rantingrick, 23.01.2011 01:07:
I have in many threads declared that Tkinter (and TclTk) is currently
--and has been for a decade-- the wrong choice for Python's stdlib
GUI. [...]
It is time to prove once and for all how dated and worthless Tkinter
is compared to wxPython.
What's the aim of tha
From: "rantingrick"
>
> WxPython versus Tkinter (A code battle to the death!)
>
> by Rick Johnson.
>
> I have in many threads declared that Tkinter (and TclTk) is currently
> --and has been for a decade-- the wrong choice for Python's stdlib
> GUI. Throughout the 90's Tkinter was fine. However
On 1/22/2011 7:07 PM, rantingrick wrote:
Near the beginning of this thread, I gently challenged you to produce a
concrete, practical proposal for an stdlib addition that could be
critiqued and improved. When you asked for problems with
wxwidgets/wxpython, I gave some. Still waiting.
So PUT
WxPython versus Tkinter (A code battle to the death!)
by Rick Johnson.
I have in many threads declared that Tkinter (and TclTk) is currently
--and has been for a decade-- the wrong choice for Python's stdlib
GUI. Throughout the 90's Tkinter was fine. However we have been in the
21st century for
11 matches
Mail list logo
