Let's make May a datatype month for AmigaOS 4. I'm calling on those brave members of the AmigaOS 4 to spend some time in May focused on producing, updating, or helping with data types.
The scope would be to develop a new datatype for us, find datatypes on the OS4 Depot, grab and recompile the open-source ones, and modernize the codebase. Of course, not everyone has the skill to write or read code to do these things, but AI can.
I will be using AI tools, and we'll try to create at least one new datatype in May. I would be happy to help others leverage the same tools so they, too, can create new datatypes for the Amiga computer. AI is so powerful. You can ask it to create a datatype that works across all flavors of AmigaOS. My focus is on OS 4, but I welcome anybody who wants to support all Amiga platforms.
Some ideas for new datatypes the Amiga could use include a Markdown data type, a camera RAW datatype, and a datatype supporting popular formats and applications like Microsoft Word. I realize that sounds wild, but the Word format is a published spec. AI could take that spec and create a viewer. I'm sure there are dozens of other datatypes that the Amiga platform could use that we don't currently have.
What I'm asking in this thread is for you to post a message indicating which datatype you want to work on so we don't duplicate efforts, to suggest a new data type the Amiga computer needs, or to offer support and testing for datatypes.
What's out of scope for this thread? Is complaining about datatypes, or about the datatype system not supporting streaming? The goal here is to move the boing ball forward and bring more capabilities to the AmigaOS 4 and other Amiga platforms.
Not sure what, multiview support regarding font size, bold, and italic and so on, while you can read markdown no problem, you might want to generate a image format, to support UTF8 and all the formatting, but that is kind of a memory hungry solution. Or maybe you just want something converts it into ASCII 8bit encoded text, that can be loaded as a readable format without all that.
Maybe a making MD viewer is more appropriate action. Markdown support URL’s to images and tables, and links to web sites.
Its not a simple project, in particularly if need to display different parts of the documents with different fonts based on UTF8 codes ranges (See the Unicode table). But anyway 50% is better then 0% markdown support.
Not sure what the best approach is, its definitely good idea to have strategy before you start. Or maybe there is existing project that can be ported over, it can save you lot of hazel.
Reading MD, before reinventing the wheel best to look into following projects.
Not sure what, multiview support regarding font size, bold, and italic and so on, while you can read markdown no problem, you might want to generate a image format, to support UTF8 and all the formatting, but that is kind of a memory hungry solution. Or maybe you just want something converts it into ASCII 8bit encoded text, that can be loaded as a readable format without all that.
AmigaOS 4.x supports 32 bit Unicode text rendering incl. the usual bold, italic, underline, strike-trough, etc. styles, as well as subpixel rendering (unless the locale is set to USA or Canada or something else where patents regarding it apply and prevented enabling it in AmigaOS). Check for example my text functions in OWB, using only AmigaOS 4.x functions (diskfont and graphics.library), no external libraries like libfreetype used/required.
Even more than 30 years ago Unicode and outline fonts with all styles were already supported, IIRC since AmigaOS version 2.1, but limited to 16 bit Unicode in the included AGFA Intellifont font engine (bullet.library). What both AmigaOS 2.1+ and 4.x are missing is support for colour outline fonts. Required for example for current web browsers to display coloured emoji, but for a lot of other use cases the B/W implementations might still be enough.
almost forgot Anime datatypes are interactive, mostly use libpng, for image loading, but then again if do load any image, it some old code I wrote years ago.
Edited by LiveForIt on 2026/5/3 19:28:32
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
My selfish goal is to get more folks, like me who are not developers to embrace AI coding to produce AmigaOS 4 software.
Of course no need to use AI, but not using AI to accelerate the grunt work of parsing an open source format seams like a labor of love or a waste of time :)
I checked OS4depot and I'm going to modernize and extend the font datatype. We'll see how it goes.
A Model Context Protocol server for driving AmigaOS 4.1 machines — both QEMU guests and real PowerPC hardware — from MCP-aware clients such as Claude Code, Claude Desktop, and IDE plugins.
At a glance Brings AmigaOS 4.1 inside your AI client. From a single MCP session you can:
• Browse and edit files on the target Amiga, run AmigaDOS commands with captured stdout, upload large binaries with zlib compression and resumable chunks. • Inspect live state — running tasks, opened libraries, mounted volumes, public screens, the last alert (decoded), CPU + cache + AttnFlags. • Drive QEMU lifecycle — start, stop, screenshot the framebuffer, save / restore VM snapshots, attach a GDB stub for whole-system debug. • Coordinate a fleet — run one method across any mix of QEMU guests and real hardware in parallel; barrier, quorum, or cross-target file relay. • Install AmigaOS 4.1 FE end-to-end onto a blank volume — preflight, ISO mount, copy, LHA extract, Kicklayout patch, verify — via a single installer.run call. • Live X5000 hardware introspection — board / CPU temperatures, voltages, fan PWM/RPM via the Cyrus MCU, plus CCSR registers, TLB walks, and IDebug-driven per-task crash snapshots.