What does your OS look like? (Screen Shots..)

[CorruptedByCPU]

At last, transparency :]
https://blackdev.org/files/cyjon.raw

Code: Select all

qemu-system-x86_64 -enable-kvm -drive format=raw,file=cyjon.raw -m 32 -rtc base=localtime

[Kamal123]

Added taskbar and a clock..








-----
https://github.com/manaskamal/aurora-xeneva
[email protected]

[sleephacker]

When I started osdev I set myself the challenge that all executable code of at least my kernel had to be generated using only NASM and any self-written tools. So, I've been working off-and-on on my own 'programming language' (although it's closer to an advanced pre-processing language for assembly than it is to an actual new programming language). It's essentially 'high-level' assembly including variables, control flow statements, functions, and recently structs and (non-static) methods. A true freak of nature.

The following image is of some test code running (demonstrating structs, methods and for-loops):

The code used to generate the above image:

Code: Select all

Graphics.Rectangle [myRectangle] = Graphics.Rectangle.NewRectangle(100, 150, 200, 250) # allocate & initialise a Rectangle struct

# fluctuate background color between orange and pink, and call myRectangle's Draw() method
colorLoop:
	forbe(byte [green] = 0; cmp [green], 127; inc [green]) # the 'be' in 'forbe' indicates that the for-loop should continue as long as the below/equals condition is met, analogous to the letters 'be' in the 'jbe' instruction
	{
		mov al, 127
		sub al, [green]
		Graphics.fillScreen([buffer], 255, [green], al)
		[myRectangle].Draw([buffer])
		Graphics.copySSE([buffer], [Graphics.framebuffer], [Graphics.frameSize])
	}
	forbe(byte [blue] = 0; cmp [blue], 127; inc [blue])
	{
		mov al, 127
		sub al, [blue]
		Graphics.fillScreen([buffer], 255, al, [blue])
		[myRectangle].Draw([buffer])
		Graphics.copySSE([buffer], [Graphics.framebuffer], [Graphics.frameSize])
	}
	jmp colorLoop

I'm parsing this using a Python library called Arppeggio, and the parse-tree is then compiled/transpiled into assembly code by a compiler (or whatever I should call it) I wrote from scratch in C#, after which the result is assembled using NASM.

[segfaultdev]

Got DOOM (kinda) working!

(DOOM kinda working)

I wrote a tiny shell too, with some builtin commands and file loading abilities. Oh, and I also wrote a background program that gets called on kernel panics, CPU exceptions and all kinds of system errors.

(shell help and kernel panics)

nop9.png (6.66 KiB) Viewed 13965 times

And the terminal emulator(communicates with the video and keyboard drivers through a really simply IPC system) supports ANSI escape codes too!

(opening files and ansi escape codes)

nop8.png (11.7 KiB) Viewed 13965 times

Here's the entire OS, in case you wanna check it:
https://github.com/segfaultdev/nop

[Kamal123]

Created a new calculator app for Xeneva



Here's the repository-
https://github.com/manaskamal/aurora-xeneva

[Kamal123]

Here's my os with new updates and bug fixes. Now the graphics library supports basic True Type fonts rendering.

I am also looking for contributors, who will join the project and make the project not only for me but for 'us' . Here's my link - https://github.com/manaskamal/aurora-xeneva

[klange]

Here's my os with new updates and bug fixes. Now the graphics library supports basic True Type fonts rendering.

I am also looking for contributors, who will join the project and make the project not only for me but for 'us' . Here's my link - https://github.com/manaskamal/aurora-xeneva

I went to look at your code because it seems like you are not connecting the start and end points of your curves and I wanted to see if I could figure out what you missed, and you can imagine how utterly disappointed I was to find that you stole "your" TrueType implementation from me, despite a very straightforward permissive license. Since you are looking for contributors, you should have no trouble rectifying this situation by adding the required copyright and license information to the file.

Anyway, back to the "not connecting start and end points" problem... Take a look at this bit of code that processes curves, your modified version is immediately drawing lines between the points, so you miss the implicit connection between the start and end, along with being entirely wrong about the shape of the curve because you dropped the parts that actually handle the curve calculations. It actually looks like you copied all of my rendering code but you're only using the coordinate parser...

[Kamal123]

Here's my os with new updates and bug fixes. Now the graphics library supports basic True Type fonts rendering.

I am also looking for contributors, who will join the project and make the project not only for me but for 'us' . Here's my link - https://github.com/manaskamal/aurora-xeneva

I went to look at your code because it seems like you are not connecting the start and end points of your curves and I wanted to see if I could figure out what you missed, and you can imagine how utterly disappointed I was to find that you stole "your" TrueType implementation from me, despite a very straightforward permissive license. Since you are looking for contributors, you should have no trouble rectifying this situation by adding the required copyright and license information to the file.

Anyway, back to the "not connecting start and end points" problem... Take a look at this bit of code that processes curves, your modified version is immediately drawing lines between the points, so you miss the implicit connection between the start and end, along with being entirely wrong about the shape of the curve because you dropped the parts that actually handle the curve calculations. It actually looks like you copied all of my rendering code but you're only using the coordinate parser...

Yes, I took toaruos true type implementation as guide for learning but the mistake I did was not mentioning the name of toaruos and pushing it to my repository. I am sorry. I will immediately remove the entire ttf.cpp and I will write in future. And also I will mention toaruos on my source code and repository. I am really sorry for that.

[MollenOS]

Been working these past months rebuilding my user environment, porting build systems to cmake and fixing a lot of bugs. My new window compositor now runs again, and yes it runs doom!

[klange]

Been working these past months rebuilding my user environment, porting build systems to cmake and fixing a lot of bugs. My new window compositor now runs again, and yes it runs doom!

Meulengracht! Great to see updates on MollenOS!
I wanted to try it out but I noticed the "download" page for 0.6 from earlier this year has no download links.
Since you've got a Github Actions setup going, I highly recommend setting it up to upload artifacts. It's free nightly builds!

[MollenOS]

Been working these past months rebuilding my user environment, porting build systems to cmake and fixing a lot of bugs. My new window compositor now runs again, and yes it runs doom!

Meulengracht! Great to see updates on MollenOS!
I wanted to try it out but I noticed the "download" page for 0.6 from earlier this year has no download links.
Since you've got a Github Actions setup going, I highly recommend setting it up to upload artifacts. It's free nightly builds!

Thank you klange! The past 6 months have been redoing many things and have had very few actual updates (that are visual), but a lot has changed for the mollenos ecosystem! You've discovered my weakness. Websites. I hate building them and hate maintaining them, thus explaining why it's so behind!

I do have it on my TODO to build images nightly - I'll make sure to get it done asap! I don't know why I've slacked on this point!

[eekee]

I'm parsing this using a Python library called Arppeggio, and the parse-tree is then compiled/transpiled into assembly code by a compiler (or whatever I should call it) I wrote from scratch in C#, after which the result is assembled using NASM.

Cool work. It used to be normal for compilers to generate assembly language and call the assembler to produce the object code, so I don't think you need to call it a transpiler.

[sed4906h]

Not exactly much to show yet now that I'm trying to reimplement everything for x86_64, but the Rotom is too good to not show off.

Here's the logo on its own, which is based off a post by daily-haunted-tv.

To make the text, I just drew it crudely in mspaint and (like the rotom icon) moused over key points to find coordinates. Here's the original.

[klange]

[eekee]

@sed4906h: That cracks me up! My tired brain looked at it as boring old text mode, then, "Oh hey, graphics! Wait... he implemented graphics support to draw that?" But I guess you're using UEFI's framebuffer?

@klange: 2.0!