Hello again,
Building on the previous discussion about deep API-level integration for 68k applications, I'd like to propose a complementary strategy for handling the vast library of self-contained 68k software like games, demos, and legacy programs: a unified content launcher system built into the Workbench.
This would provide a seamless "double-click and run" experience for everything from ADF disk images to WHDLoad slaves, directly from the Zune desktop.
The General Concept
The user would have an icon for each piece of 68k software (e.g., "Sensible World of Soccer.info"). Double-clicking this icon would instantly launch the game in a pre-configured Janus-UAE instance, running within a window that could feature modern visual enhancements like CRT shaders and bezels.
Technical Implementation Strategy
This can be achieved by leveraging and extending existing AROS technologies:
Step 1: The Icon (.info) as a Configuration Database
The AROS .info file is perfect for this. We can define a new set of Tool Types specifically for Janus-UAE. An icon's Tool Types would describe everything needed to run the software under it.
Example Tool Types for a WHDLoad game:
; The launcher that will handle this icon
DefaultTool=C:JanusLauncher
; --- JanusLauncher Configuration ---
JANUS_CONTENT_PATH=Games:WHDLoad/S/SensibleSoccer/SensibleSoccer.slave
JANUS_CONTENT_TYPE=WHDLOAD
JANUS_TARGET_MODEL=A1200
JANUS_CHIPSET=AGA
JANUS_CPU=68020
JANUS_FAST_MEM=8
JANUS_PRELOAD_FILES=DH1:AmigaOS/C,DH1:AmigaOS/S
JANUS_SHADER=Shaders:CRT/crt-geom-deluxe.slang
JANUS_BEZEL=Images:Bezels/amiga1084s_bezel.png
This approach is flexible enough to define configurations for ADF, HDF, CD32 ISOs, or even specific 68k executables.
Step 2: A Centralized Handler (JanusLauncher)
A single script or small C application, C:JanusLauncher, would be the core of this system. When an icon is double-clicked, JanusLauncher would:
* Parse the Icon: Read all JANUS_ Tool Types from the .info file that was clicked.
* Generate a Configuration: Dynamically create a temporary emulator configuration file (e.g., in T:) based on the parsed Tool Types. This is cleaner than using a massive command-line string.
* Launch the Emulator: Execute janus-uae.exe -f T:temp-config.uae.
* Cleanup: Once the emulator closes, the temporary config file is deleted.
This creates a highly customizable system where users (or automated scripts) can easily create icons for their entire software library.
Step 3: Enhancing the Emulator's Rendering
To deliver a truly polished experience, the Janus-UAE instance used for this purpose would need enhancements:
* Shader Support: Integrate a modern, flexible shader pipeline (like GLSL/Slang, learning from FS-UAE or RetroArch). This would allow users to apply realistic CRT effects, scanlines, or other visual improvements.
* Bezel/Overlay System: Implement a simple overlay system that can render a PNG image (like a monitor or TV bezel) around the emulated screen.
* On-the-fly Menu: A right-click on the emulator window's title bar or a hotkey could bring up a native Zune context menu to change shaders, toggle bezels, or adjust other settings in real-time.
The most ambitious version of this could even render the emulated screen on a texture within a 3D-rendered scene showing a classic Amiga monitor on a desk, but a 2D bezel system is a more realistic first step.
Benefits of this Approach:
* Total Integration: The user never has to manually open an emulator and configure it. Their 68k library lives as native-looking icons on their AROS desktop.
* Extreme Configurability: Every single program can have a perfectly tailored hardware configuration, ensuring maximum compatibility.
* Aesthetic Appeal: The addition of modern visual features like shaders and bezels would make running legacy software on AROS a premium experience, surpassing what many other platforms offer out-of-the-box.
* Separation of Concerns: This system handles "sandboxed" legacy software, while the previously discussed API-retargeting can focus on "productive" applications that need to integrate with the native OS.
Together, these two proposals could create a comprehensive strategy for making AROS the ultimate environment for both classic and modern Amiga computing.
What are your thoughts on the feasibility of this launcher system?
Best regards,
GermánCMan
AMIGASYSTEMDistro Maintainer