Repository navigation
IDLE: enable editor, shell, debugger integration in one window #69014
Description
| BPO | 24826 |
|---|---|
| Nosy | @terryjreedy, @kbkaiser, @serwy, @roseman |
| Dependencies |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2015-08-07.14:29:08.541>
labels = ['expert-IDLE', 'type-feature', '3.10']
title = 'ability to integrate editor, shell, debugger in one window'
updated_at = <Date 2020-06-06.15:59:56.204>
user = 'https://github.com/roseman'bugs.python.org fields:
activity = <Date 2020-06-06.15:59:56.204>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['IDLE']
creation = <Date 2015-08-07.14:29:08.541>
creator = 'markroseman'
dependencies = ['9262', '24760']
files = []
hgrepos = []
issue_num = 24826
keywords = []
message_count = 7.0
messages = ['248195', '248243', '248284', '248307', '248464', '248467', '298318']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'kbk', 'roger.serwy', 'markroseman', 'Al.Sweigart']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue24826'
versions = ['Python 3.10']
Activity
roseman commentedon Aug 7, 2015
This builds on things like the tabbed editor suggestion, but essentially I'm talking about a scenario where you'd have your one (editor) window open working on your program, you click 'run...' or 'debug...' from the menu, and a shell and debugger area open up at the bottom of that one window, and you can resize that area.
This is analogous to what happens if you click 'inspect element' in most web browsers nowadays.
Getting rid of the *need* for multiple windows would help simplify a lot of things.
terryjreedy commentedon Aug 8, 2015
Many of us want to reorganize Idle from multiple windows, some with menus, to one window with multiple frame or panes. The initial steps:
a) create a new application window with an application menu. (I believe OSX partially forces this on Macs anyway.) The menu should have items added or deleted, or just activated or not, according to the active window and other conditions. Adjust the menu construction functions, including the ones used in extension files, accordingly.
b) remove the menu and Toplevel from the base editor window used for editor, shell, and output. Leave frame that can be added to other containers, whether Toplevel, Frame, Paned Window, or Notebook.
c) remove the Toplevel from dialogs that we think should be non-modal and insertable into containers. I think the debugger, as you say, aumented config dialog, and improved search/replace dialog, are all candidates for this treatment.
I think users, or at least class instructors, should have some control over placement. There definitely should not be a single, locked down design.
roseman commentedon Aug 8, 2015
Yes that's exactly what I was thinking. If everything is a frame rather than a toplevel it'll be much easier to reconfigure things.
AlSweigart commentedon Aug 9, 2015
Is this a duplicate of https://bugs.python.org/issue9262 Either way, there's some good discussion there and also on https://bugs.python.org/issue24750 (ctrl-f for "tabbed")
terryjreedy commentedon Aug 12, 2015
bpo-9262 is step b) above, and therefore a dependency for this issue.
terryjreedy commentedon Aug 12, 2015
bpo-24760 - config dialog not modal, is part of c)
terryjreedy commentedon Jul 13, 2017
https://www.youtube.com/watch?v=nO78ECRighw shows IDLE on Mac with a shell and editor window. Because Mac pulls the menu off of each window and puts one above both, which are side by side, it looks like an example of what we want to have on all systems.
[-]ability to integrate editor, shell, debugger in one window[/-][+]IDLE: enable editor, shell, debugger integration in one window[/+]