text stringlengths 0 888 |
|---|
- Store breakpoints in a global (per-project) database (GvR); Dirk |
Heise adds: save some space-trimmed context and search around when |
reopening a file that might have been edited by someone else. |
- Capture menu events in extensions without changing the IDLE source. |
(Matthias Barmeier) |
- Use overlapping panels (a "notebook" in MFC terms I think) for info |
that doesn't need to be accessible simultaneously (e.g. HTML source |
and output). Use multi-pane windows for info that does need to be |
shown together (e.g. class browser and source). (Albert Brandl) |
- A project should invisibly track all symbols, for instant search, |
replace and cross-ref. Projects should be allowed to span multiple |
directories, hosts, etc. Project management files are placed in a |
directory you specify. A global mapping between project names and |
project directories should exist [not so sure --GvR]. (Tim Peters) |
- Merge attr-tips and auto-expand. (Mark Hammond, Tim Peters) |
- Python Shell should behave more like a "shell window" as users know |
it -- i.e. you can only edit the current command, and the cursor can't |
escape from the command area. (Albert Brandl) |
- Set X11 class to "idle/Idle", set icon and title to something |
beginning with "idle" -- for window manangers. (Randall Hopper) |
- Config files editable through a preferences dialog. (me) DONE |
- Config files still editable outside the preferences dialog. |
(Randall Hopper) DONE |
- When you're editing a command in PyShell, and there are only blank |
lines below the cursor, hitting Return should ignore or delete those |
blank lines rather than deciding you're not on the last line. (me) |
- Run command (F5 c.s.) should be more like Pythonwin's Run -- a |
dialog with options to give command line arguments, run the debugger, |
etc. (me) |
- Shouldn't be able to delete part of the prompt (or any text before |
it) in the PyShell. (Martijn Faassen) DONE |
- Emacs style auto-fill (also smart about comments and strings). |
(Jeremy Hylton) |
- Output of Run Script should go to a separate output window, not to |
the shell window. Output of separate runs should all go to the same |
window but clearly delimited. (David Scherer) REJECT FIRST, LATTER DONE |
- GUI form designer to kick VB's butt. (Robert Geiger) THAT'S NOT IDLE |
- Printing! Possibly via generation of PDF files which the user must |
then send to the printer separately. (Dinu Gherman) FIRST CUT |
Writing an IDLE extension |
========================= |
An IDLE extension can define new key bindings and menu entries for IDLE |
edit windows. There is a simple mechanism to load extensions when IDLE |
starts up and to attach them to each edit window. (It is also possible |
to make other changes to IDLE, but this must be done by editing the IDLE |
source code.) |
The list of extensions loaded at startup time is configured by editing |
the file config-extensions.def. See below for details. |
An IDLE extension is defined by a class. Methods of the class define |
actions that are invoked by event bindings or menu entries. Class (or |
instance) variables define the bindings and menu additions; these are |
automatically applied by IDLE when the extension is linked to an edit |
window. |
An IDLE extension class is instantiated with a single argument, |
`editwin', an EditorWindow instance. The extension cannot assume much |
about this argument, but it is guaranteed to have the following instance |
variables: |
text a Text instance (a widget) |
io an IOBinding instance (more about this later) |
flist the FileList instance (shared by all edit windows) |
(There are a few more, but they are rarely useful.) |
The extension class must not directly bind Window Manager (e.g. X) events. |
Rather, it must define one or more virtual events, e.g. <<z-in>>, and |
corresponding methods, e.g. z_in_event(). The virtual events will be |
bound to the corresponding methods, and Window Manager events can then be bound |
to the virtual events. (This indirection is done so that the key bindings can |
easily be changed, and so that other sources of virtual events can exist, such |
as menu entries.) |
An extension can define menu entries. This is done with a class or instance |
variable named menudefs; it should be a list of pairs, where each pair is a |
menu name (lowercase) and a list of menu entries. Each menu entry is either |
None (to insert a separator entry) or a pair of strings (menu_label, |
virtual_event). Here, menu_label is the label of the menu entry, and |
virtual_event is the virtual event to be generated when the entry is selected. |
An underscore in the menu label is removed; the character following the |
underscore is displayed underlined, to indicate the shortcut character (for |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.