Return to TODO CVS log

Up to [Previous NeXT emulator] / previous / python-ui

Annotation of previous/python-ui/TODO, revision 1.1

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

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