Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #55505 > unrolled thread

Re: IDLE: A cornicopia of mediocrity and obfuscation.

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: IDLE: A cornicopia of mediocrity and obfuscation. rantingrick <rantingrick@gmail.com> - 2011-02-01 08:18 -0800
    Re: IDLE: A cornicopia of mediocrity and obfuscation. Cousin Stanley <cousinstanley@gmail.com> - 2011-02-01 19:03 +0000
    Re: IDLE: A cornicopia of mediocrity and obfuscation. Terry Reedy <tjreedy@udel.edu> - 2011-02-01 14:15 -0500

#55505 — Re: IDLE: A cornicopia of mediocrity and obfuscation.

On Feb 1, 9:54 am, Terry Reedy <tjre...@udel.edu> wrote:
> On 2/1/2011 12:13 AM, rantingrick wrote:
>
> > On Jan 31, 4:17 pm, Kevin Walzer<k...@codebykevin.com>  wrote:
> >> Rick,
> > Yes. IDLE is first and foremost a tool to get work done. However we
> > should not ignore the fact that IDLE could also be a great learning
> > resource for Tkinter GUI's and other subjects. Why not clean up the
> > code base? We could start small. First, move the custom widgets like
> > textView, Tabbedpages, FindDialog, ReplaceDialog, and TreeWidget into
> > the lib-tk for others to use more freely. Then we can modify the
> > "event robbers" CallTips, ParenMatch, and ColorDelegator.
>
> Perhaps, after the repository moves from svn to hg, some 'we' will.

Well the best attribute of IDLE is backward compatibility -- there is
none to worry about. IDLE is not a module with an interface, it's just
a tool. So we could change anything we want without worry of causing
code breakage. There is not good reason NOT to fix IDLE.

> Maybe Kevin would help a bit.

I was hoping he would get involved however his last post proved
otherwise. I know he has his own projects however he would have been a
valuable asset for the ttk theming stuff.

> Such a project would be carried out on the tracker and idle-sig mailing
> list. Normal decorum would be required -- no ranting or insulting. The
> first thing to do, in my opinion, is to review existing patches on the
> tracker.

Agreed. Terry (or anyone) can you give some link to info on "hg" so i
can study up on this topic? Thanks

> > Well some changes and improvements can be made to the UI as well.
>
> There is patch on the tracker, by G. Polo, as I remember, to replace tk
> widgets with the newer themed ttk widgets. It needs to be reviewed and
> tested. To make a big change (or proceed with any refactoring) better
> automated testing would be very useful.

Yes "turning on" the themes would be a huge improvement. I also wished
IDLE would look better.

[toc] | [next] | [standalone]

#55751

rantingrick wrote:

> Terry (or anyone) can you give some link to info on "hg" 
> so i can study up on this topic ?

  http://mercurial.selenic.com/


-- 
Stanley C. Kitching
Human Being
Phoenix, Arizona

[toc] | [prev] | [next] | [standalone]

#55971

On 2/1/2011 11:18 AM, rantingrick wrote:

> Well the best attribute of IDLE is backward compatibility -- there is
> none to worry about. IDLE is not a module with an interface, it's just
> a tool. So we could change anything we want without worry of causing
> code breakage. There is not good reason NOT to fix IDLE.

That is similar to my view. Of course, there will be an tracker issue 
and list discussion for any major change. I have even thought it should 
perhaps be moved to the Tools/ directory, but installation of that is 
optional. Google codesearch can be used to see what, if anything, anyone 
imports from idlelib.

> Agreed. Terry (or anyone) can you give some link to info on "hg" so i
> can study up on this topic? Thanks

Joel Spolsky's tutorial is highly regarded as an easier intro than the 
reference manual. I am about to reread it myself.
http://hginit.com/

-- 
Terry Jan Reedy

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web