OSDev.org

Sometimes you have to take a step back to move forward! Nice font, by the way.

Basic OS Update:
+Etnox Compositor
->can draw desktop
->can draw windows
->can process mouse
->initial release 0.1

Is the window movable? Can you have multiple windows with some kind of "focused window" logic?

Not the best photo, but serves my purpose. I just implemented a way to draw multiple "screens" in the video output. I already had a class to represent the screen, so I changed my display class to be able to draw more then one screen (I can also choose the position in x-y coordinates). In the photo I set the display resolution to 1920x1080 and drawn a 800x600 screen at 100x100.

This can be useful in situations where you want to have two separate screens (e.g. one for the console and the other to display graphical information). You could also have multiple consoles (obviously having a graphical interface also solves all these cases )

Finally finished adding complete paging
My kernel will stay a lower half kernel, higher half has nearly no advantages for me.
I load all of my apps to 0xC0000000 now which means one applications address space can be a maximum of 1gb.
All the malloced stuff will still go below the virtual 3gb border.

To test everything I ported some apps I wrote on windows before, on the screenshot you can see my snake port runs pretty fine

@Ch4ozz you use FreeType to render text or use your own algorithm to render them?
.BIN shall be renamed in some other extension, through since it's mostly used for pure binary files.

Well Im gonna change it to .elf or .exe then (I might support PE files soon)
Im using a modified version of stb_truetype (https://github.com/nothings/stb)
Porting freetype was too much work imo

Not (yet). I have that in plan.

My GUI, showing the terminal emulator, a widget test application, and a pretty successful run of Snake

Awesome!
You already added all the stuff I still have to add

Wrote a file system implementation, implemented open(), close(), seek(), tell() and read(), fixed a few bugs in my block device manager along the way. And of course, the best reward of a file system is that it lets me use a picture file as the background, and that lets me post in this thread, lol.
Next up on my to-do list: executing programs from disk. I already have capability to execute programs from memory, and so loading from disk wouldn't be more than a few file system calls, and then doing the same as I do to load from memory.
EDIT: Forgot to say this, QEMU is emulating a SATA hard disk here.

Bravo! You finally done SATA, IDE and filesystems for your OS!
Based on source-code, add executable support and move GUI away from kernel... Althrough you will need some work to use stack in them seperately, through...

Finally, after it being on my TODO list for nearly five years, ToaruOS has ATAPI CD and ISO 9660 FS support, so the live CDs can read their host media. My ISO 9660 implementation is fairly minimal, not yet supporting the Rock Ridge or Joliet extensions, hence the short filenames in this screenshot (I'll get around to Rock Ridge eventually). I took the Linux approach of forcing these filenames to lowercase for display purposes, as compliant implementations should only write UPPER CASE file names and those are ugly (I know recent versions of xorriso are writing lower case names, though; quite odd!). In building this, I discovered a completely unrelated bug in my compositor and image viewer when trying to run it in QEMU, but that's a story for another thread. Screenshot is of VirtualBox on Windows as I was also testing my toolchain under WSL (it works with a minor patch). Showing the wallpaper I use in GRUB on my CDs, which is a darkened and scaled version of the one I use generally: a photo I took of Yosemite (it's darkened so the white text of the bootloader menu is legible).

Incredible! ToaruOS never ceases to amaze and inspire me on my own OS projects. Keep up the good work!

Thanks!
I don't plan to move the GUI away from the kernel; the core functionality will always be in the kernel. Userspace applications can then use this functionality to make their own looks. I also have plans of an API that lets userspace applications write directly to the display (non-windowed applications) but this is not the time for that yet.