dos-like
dos-like-rs
dos-like | dos-like-rs | |
---|---|---|
9 | 1 | |
972 | 12 | |
- | - | |
3.9 | 6.1 | |
about 2 months ago | 7 months ago | |
C | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dos-like
-
Dos-like: Engine for making things with a MS-DOS feel, but for modern platforms
I’m assuming “DOS feel” means there’s no dynamic linker so the implementation has to be contained in header files?
-
Writing bindings to `dos-like` for Rust: some lessons learned
So when I had some spare time the past weekend, I decided to do something a bit different: bring to Rust an existing framework that lets you write applications which look like they are DOS applications. dos-like, made by Mattias Gustavsson, is like a small engine for writing modern applications with the look & feel of MS-DOS programs. So basically, when using this framework, we end up with applications that run on modern hardware and operating systems all the same, but with deliberate video effects and audio that bring us back to that era, including large pixels, CRT distortion, text and graphics video modes, and synthesized (Sound Blaster 16) or MIDI (Sound Blaster AWE32) music. It was written in C, mostly as a single file with some other statically linked dependencies. The project also comprises a few fun examples, such as a proof-of-concept FPS inspired by Wolfenstein 3D, a point-and-click adventure, a voxel renderer, and even a music tracker.
dos-like-rs
-
Writing bindings to `dos-like` for Rust: some lessons learned
By creating direct bindings to the C interface (dos-like-sys), followed by a more high-level abstraction, it becomes possible and (hopefully) intuitive to write applications of this sort in Rust! So I did that! In this post, I will now share a small collection of technical topics that I felt worth sharing about the conception of these bindings.
What are some alternatives?
cool-retro-term - A good looking terminal emulator which mimics the old cathode display...
rusty-dos - A Rust skeleton for an MS-DOS program for IBM compatibles and the PC-98, including some PC-98-specific functionality
impulsetracker - Fork/clone of https://bitbucket.org/jthlim/impulsetracker // Full source code for Impulse Tracker, including sound drivers, network drivers, and some supporting documentation // IMPORTANT: This is neither the official repository (upstream at bitbucket.org appears deleted by now!) nor hosted or owned by Jeffrey Lim!
wajic - WebAssembly JavaScript Interface Creator
textual - The lean application framework for Python. Build sophisticated user interfaces with a simple Python API. Run your apps in the terminal and a web browser.
schismtracker - An oldschool sample-based music composition tool.
cursesjs - An implementation of ncurses for the web browser
Gui.cs - Cross Platform Terminal UI toolkit for .NET
rust-bindgen - Automatically generates Rust FFI bindings to C (and some C++) libraries.
jexer - Java Text User Interface. This library implements a text-based windowing system loosely reminiscent of Borland's Turbo Vision system