Javascript libraries for parsing and rendering binary Habitat image files
All binary image files in the habitat repository, organized by where they were found in the repo, and deduplicated
A web frontend for browsing and viewing in detail all Habitat image files, including animations and avatars
Javascript libraries for parsing Neohabitat JSON files and Habitat Muddle files (beta.mud)
All JSON region files copied from the Neohabitat repository
The beginning of a web frontend that parses Neohabitat JSON files, correlates objects with the Habitat Muddle beta.mud file, and displays Habitat regions. This should be fairly straightforward to extend to a full-featured visual web-based region / object editor.
mamelink, a reimplementation of the fastlink C API that can interface with MAME via a Lua plugin
An incomplete / nonworking port of fred to modern C / Unix
No external dependencies are required, though currently all libraries assume they are running in a fairly recent browser environment. Offline rendering with node.js or deno may be desirable in the future and would require some small tweaks.
Currently known to be missing / incomplete:
Text rendering
Horizontal object flipping
Trapezoid / super trapezoid object support
Container object support
Accurate color RAM emulation when rendering full scenes
Very open to suggestions about how best to organize everything (ie. it might make sense for the mamelink / fred work to go in its own branch or repo).
Addresses https://github.com/frandallfarmer/neohabitat/issues/141 and contributes towards https://github.com/frandallfarmer/neohabitat/issues/439.
This PR includes:
beta.mud)beta.mudfile, and displays Habitat regions. This should be fairly straightforward to extend to a full-featured visual web-based region / object editor.mamelink, a reimplementation of the fastlink C API that can interface with MAME via a Lua pluginfredto modern C / UnixNo external dependencies are required, though currently all libraries assume they are running in a fairly recent browser environment. Offline rendering with node.js or deno may be desirable in the future and would require some small tweaks.
Currently known to be missing / incomplete:
Very open to suggestions about how best to organize everything (ie. it might make sense for the mamelink / fred work to go in its own branch or repo).