Return to TODO CVS log

Up to [HATARI the Atari ST Emulator] / hatari / python-ui

Annotation of hatari/python-ui/TODO, revision 1.1.1.5

1.1       root        1: TODO
                      2: ====
                      3: 
                      4: This lists potential TODO items that aren't listed in the Hatari/UI
                      5: sources.
                      6: 
1.1.1.2   root        7: * Separate "Atari monitor" and "Hatari window" settings dialogs
                      8:   (move options from "Display" and monitor setting from "Machine"
                      9:   dialogs to here and add VDI options to Atari Monitor dialog)
1.1       root       10: 
                     11: * Features for Help menu:
                     12:   - Create empty floppy images (+ convert directories to hard disks?)
                     13:   - MSA converter
                     14: 
1.1.1.2   root       15: * Add more Hatari debugger features to the debug UI:
1.1       root       16:   - DSP support
1.1.1.4   root       17:   - History support
                     18:   - Profiling support
1.1.1.2   root       19:   - DSP and CPU symbols loading
1.1.1.4   root       20:   - Support for stepping the emulation (both step & next commands)
1.1.1.2   root       21:   - multiple views to memory (refreshed whenever emulation is stopped)
                     22:     - supporting also register relative views (register values
                     23:       parsing should move to common functionality first)
                     24:   - breakpoint support (issue: how to stop emulation on breakpoint
                     25:     but still allow Hatari to process remote commands?)
                     26:   - trace & debug log viewers?
1.1       root       27: 
                     28: * Put all configuration stuff into single notebook dialog?
                     29: 
1.1.1.2   root       30: * Translation support for the UI:
                     31:   - use gettext
                     32:   - build needs to build & install message catalogs
                     33:   - some way for Hatari to forward dialog ID to the remote UI
                     34:     with dialog string parameters (filenames etc) which then
                     35:     need to be localized too & shown...
                     36: 
                     37: * Hatari UI specific configuration which stores:
                     38:   - list of last used configuration files which would be shown
                     39:     either in their own menu or dialog
                     40:   - list of last used memory snapshots (10?)
                     41:   - disk image dir (uses Hatari config value as default)
                     42:   - trace settings
                     43:     - remove dialog specific load/save stuff
                     44:   - screenshot name
                     45:     - needs support also to Hatari src/screenSnapShot.c
1.1       root       46: 
                     47: * Supporting other, less important Hatari configuration options:
1.1.1.5 ! root       48:   - HD booting, toggling disk-b autoinsertion
1.1.1.2   root       49:   - something for multiple GEMDOS partition directories
1.1       root       50:   - separate A/B disk paths for images that are within ZIP archives
                     51:   - joystick autofire toggling, defining the keys for joyemu
1.1.1.2   root       52:   - keyboard repeat, key mapping type and file, mouse grabbing
1.1.1.3   root       53:   - vdi planes and size, SDL bpp forcing, spec512 threshold, ST blitter
1.1       root       54:   - cartridge image (where? it has many limitations)
1.1.1.4   root       55:   - log file and levels, console output, bios intercept, run-VBLs
1.1.1.5 ! root       56: (Many of these aren't supported by the internal Hatari UI either, or
1.1.1.2   root       57: are missing corresponding command line options so they will require
1.1.1.3   root       58: additional support on the Hatari control.c side too or they can
                     59: be only enabled at boot, not disabled.)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.