<aside> 🔥

TODO - just stubs for now

</aside>

see a detailed report of the current memory and microlibrary module (as of mar 6 2026, in the yet unreleased 0.1.6 , it might change some before release)

ReadyOS SHIM Architecture Report (v3).pdf

Control Flow → Active versus Event (Message Loop)

TODO

Small OS Shim

TODO

Apps in REU and instant suspend/resume

TODO

REU usage

• current 64K chunks, nothing OS specific, used for each APP, or one 64K per clipboard ITEM!!!, or for Specific Apps using Overlays, Starting at the beginning of REU
• Goal
  • Configurable start REU point (to coexist with ramdisk, Geos, C64os etc)
  • 16KB chunks (and apps can use within that)
  • Clipboard manage its own smaller memory within.. so it likely can just one ONE chunk , or request more chunks when needed
  • as OS level chunk(s) - more App info from RAM to REU, add common current “runtime” settings, plus config settings, themes, REU Map (rather than in the RAM shim)
  • Micro libraries beyond current REU, so apps can use Heaps, and Overlays

Micro Libraries

• the OS shim is under 1KB designed to coordinate app switching, Most everything is is based on micro libraries apps can choose to use.. some are OS level, others a murky level between OS, Others part of the common look and feel but really app but app, and others purely App level.
  • Core
    • Playing into the suspend/resume mechanisms - dealing with hotkeys to go back to launcher, and next/last app
    • smallest part of REU (another micro library for Apps managing their own REU allocations)
  • Murky
    • Clipboard (getting and setting)… these things are 100% consistently common, but not every app is going to use the clipboard.. also the clipboard manager will use micro libraries (like to delete from the history) that apps don’t need to use to just copy/paste. Also later apps might opt into a Paste from history , with a way to seleect not just the last item to paste.
    • REU - app level, app overlays, app heaps - really doesn’t have to be consistent (could have many competing micro libraries) as long as it stays within the main 16K allocations
    • Hotkey library - not yet done, now its wild west within each app.. but something to have a consistent pattern
  • Common App
    • the TUI microlibraries which are many.. however the common look at feel, doesn’t have to be the same, and there can be multiple. eg the current thing is really lowercase only.. we may want ones that have mixed upercase/lowercase , custom character sets. different ways to do menuing.. and even full text one,

Common readyOS Overlays

• right now things like file/open save dialogs are common libraries bound to each app that uses them, however there may be value in making these common overlays, that apps could use that way.. paging into a specific place in memory, using them through an ABI, then moving on

Interrupt Management