itch.io

I found this tool while trying to make a custom symbol font that'd work with the ProggyClean pixel font with Dear ImGui. The tool itself works well but when I tried exporting it and loading it in my ImGui program, it was very blurry and no amount of tweaking things in the tool itself and the exported font in FontForge fixed it. To be honest, I have very little idea on how to use FontForge. I also have little idea on what the units for em size ascent descent pixel size mean and not enough patience at the time to learn it. I was trying to make a 6x12 monospaced font. (well i think proggy clean is 6x12) How would i fix this?

I should note that I found another solution to my underlying problem, by registering custom glyph rects using imgui's font api and then blitting the raw pixels for the glyphs into the font atlas. but I would also like to know how to do this using a ttf font. Maybe it'll be useful in the feature.

i'm a rock. Is this good?

i have one curiosity about the controls. why is it C to jump? in games i've played with a similar keyboard control layout it's always Z to jump. i know it's also bound to Z by default so really i don't have a problem but I'm just curious. is it like what's usually used in pico-8 games?

Holy smokes i got zero misses on invasion. In hindsight, I think i accidentally made the song 2x faster than it should be.

i think the idea is pretty cool, but the difficulty curve seems a bit uneven. i got a bit stumped on the level after the one that requires knowledge of what the dots below the flowers mean, simply because i just followed the second possible path to beat the level without understanding what the dots actually meant. also there are levels that require some thinking and then, in one instance, the next level is just you press down a single time to win. which was pretty funny but this is excusable for a game made in a mere 72 hrs

I think that this is the best game ever made. George washington would be proud.

and the choice of orange was a complete coincidence. this was long before i took up the pumpkinhead pseudonym.

the p doesn't stand for pumpkinhead, the p stands for "pOS" so the full name is "pOS pDOS"

i actually don't know what the p stands for. i got the name from a fake os i tried making on scratch like 4 years ago.  it only has a login screen. i don't remember why i chose the letter "p"

i have something you can try compiling, to demonstrate the ability to create executable files for pDOS.

it's a new builtin file, so if you already opened pDOS before you will have to reset the filesystem. do this by typing "rm -r /", refreshing the page, and typing "y" when it asks you if you want to reset. if you don't get this prompt then you'll have to delete the indexedDB database using the developer tools.

anyway when you do "ls /home" you'll see that there is a file named "hello.wat". write "dnload hello.wat", then go to the site wat2wasm demo (webassembly.github.io). once you are there, delete everything in the WAT section and then drag the "hello.wat" you downloaded, from your computer to the section. then press the "Download" button, and then drag the newly downloaded "hello.wasm" into the pDOS terminal. then finally, write "hello.wasm", and "Hello, world!" should appear on your screen.

i know that seems overly complicated, but when i finally manage to port wabt into pDOS, it'll be builtin and all you'll have to type is

wat2wasm hello.wat hello.wasm

hello.wasm

pDOS (phazrlazr.repl.co)

i finally added the help screen. most command arguments aren't implemented though.

i'm not gonna formally submit this until it's finished in probably 27 days.

i wanted to make a fake os that was actually useful as an os.

so this is basically just a shell. i mean, not what someone would think of as an os. but i was gonna make the shell and then have the graphics and windowing systems later.

i wanted to make a fake os that the user could write their own programs in. so this uses webassembly for its executable files. thinking of making it execute js files, but js isn't exactly the easiest thing to sandbox.

huge thing on my todo list is compile the webassembly compiler to webassembly itself, so that people can make executable files in the os itself. i most likely will run into problems doing that though.

also get the webassembly binary toolkit in here too. i tried doing that but i ran into problems with it trying to create a shared library, which the wasm compiler does not support. FUN.