[Idle-dev] IDLE going forward
Corey Richardson
kb1pkl at aim.com
Thu Feb 3 00:18:02 CET 2011
On 2/2/2011 5:45 PM, Douglas S. Blank wrote:
> [snip]
> I've stopped using IDLE, so I don't know if some of these issues have
> been addressed in the latest versions, but here are some things that
> were issues:
>
> * needs a stable interface for plugins (it seemed like each version
> changed slightly and our extensions kept breaking)
>
> * more hooks for plugins
>
> * needed a way to run the code in editor window without restarting the
> shell (some code has start-up code that should not have to be re-run
> each time you want to load the program)
>
> * control+p and alt+p (print and previous) were too similar and I kept
> printing the entire history
>
> * allow one to select a printer before printing
>
> * ability to clear the shell window
>
> * allow IDLE to startup with either shell or editor
>
> * Don't show the weird, scary message about Personal Firewall
> subprocessing and loopbacks. That is not a good way to introduce
> people to computing!
>
> * Allow more than one idle to be run at same time
>
> * command-line history persistent between sessions
>
> * some weird cursor positions in shell. home should take you to a
> place after prompt, not before.
>
> * cutting and pasting from shell to window could remove the >>> prompts
>
> * menu items not intuitive for beginners
>
> * more options with a context-sensitive right-mouse-click
>
> IDLE is very nice, but it could be developed into a finally-tuned
> product.
>
> Good luck!
>
> -Doug
That looks like a good list. Another good goal would be to make it so
less people say "Don't use IDLE" and decrease the general dislike. A bit
of a lofty goal, but they must have good reasons to not use idle,
otherwise they wouldn't say that...right? ;-)
More information about the IDLE-dev
mailing list