What does your OS look like? (Screen Shots..)
Re: What does your OS look like? (Screen Shots..)
Looking at new wallpapers to ship as the default, actually bothered to build libpng.
Behind the scenes, the terminal scrolls a hell of a lot faster now, and the panel shows the correct version number rather than a hardcode one.
Behind the scenes, the terminal scrolls a hell of a lot faster now, and the panel shows the correct version number rather than a hardcode one.
Re: What does your OS look like? (Screen Shots..)
Bothered? Plzklange wrote:actually bothered to build libpng.
I'm Eino Tuominen from Finland, a web software dev learning low level stuff and reading / trying out kernel dev
Re: What does your OS look like? (Screen Shots..)
Last edited by klange on Tue Oct 16, 2012 9:12 pm, edited 1 time in total.
Re: What does your OS look like? (Screen Shots..)
Was it difficult to write the compositor? I've just started planning on mine and I think I know how to do it including stuff like blitting a surface of ARGB32 onto one of RGBA24 et.c. which in itself isn't very hard to do but might prove inefficiant. Do you get descent performance?
Fudge - Simplicity, clarity and speed.
http://github.com/Jezze/fudge/
http://github.com/Jezze/fudge/
Re: What does your OS look like? (Screen Shots..)
My RGBA blitting is very inefficient, but runs okay if you don't have too many windows open. My 32-32 RGB blitting is extremely fast. Sadly, I abandoned most of my support for 24-bit display surfaces a while ago.Jezze wrote:Was it difficult to write the compositor? I've just started planning on mine and I think I know how to do it including stuff like blitting a surface of ARGB32 onto one of RGBA24 et.c. which in itself isn't very hard to do but might prove inefficiant. Do you get descent performance?
Re: What does your OS look like? (Screen Shots..)
ARM experiments: basic memory manager and scheduler
Re: What does your OS look like? (Screen Shots..)
Trinix (written in D) https://github.com/Rikarin/Trinix
Streaming OS development https://www.livecoding.tv/satoshi/
Streaming OS development https://www.livecoding.tv/satoshi/
Re: What does your OS look like? (Screen Shots..)
This is a screenshot from my little piece of code called MicroBe OS.
Aimed to "learn how things should be done". Pure x86 assembly only.
a bit more info (but a bit outdated) on http://microbe.clew.cz
Aimed to "learn how things should be done". Pure x86 assembly only.
a bit more info (but a bit outdated) on http://microbe.clew.cz
[ MicroBe OS ]
Re: What does your OS look like? (Screen Shots..)
Here is my command-line interpreter. Nothing special here. I still have a lot to do with the basic underlying OS functionality. All the GUI related things are not very current issues yet.
Re: What does your OS look like? (Screen Shots..)
Looks awesome Antti. Keep up the good work!
Fudge - Simplicity, clarity and speed.
http://github.com/Jezze/fudge/
http://github.com/Jezze/fudge/
Re: What does your OS look like? (Screen Shots..)
here's my personal project
did it in assembly on my free time.
did it in assembly on my free time.
Re: What does your OS look like? (Screen Shots..)
This is further than I got before, though still damn little compared to the rest of you. Boots in the higher half, does GDT, IDT, remaps IRQs and then redoes the paging in C++. All my code is C++ and uses namespaces throughout to separate my code. I've used PDCLIB for the majority of my C library but also took the quad parts from OpenBSDs libc so I can do arithmetic on 64 bit integers. That compiled pretty easily with only a few typedefs and disabling clang using sse etc.
Re: What does your OS look like? (Screen Shots..)
That looks really good, especially for a project done entirely in assembly in your free time.pikasoo wrote:here's my personal project
did it in assembly on my free time.
Care to share some details on your windowing system?
Re: What does your OS look like? (Screen Shots..)
i went for what i tought was the most easy, not the most efficent in memory space but every window have its own surface to write/draw to. conponent or user code write on it and the os draw it when it need.klange wrote:Care to share some details on your windowing system?
in memory i also have a zlevel buffer for every pixel on the screen, nothing like 3d stuff but a byte so unless u have more than 255 window its fine. that make it easy for drawing, when i draw my window, it mark its zlevel in that buffer for every pixel drawed. if the zlevel is already marked i test if its lower or higher. if the value is lower then its not drawed else i replace the pixel and set the new zlevel value. front windows is always zlevel 0
Re: What does your OS look like? (Screen Shots..)
MenuetOS has a skin very much like the one you use, especially on the window-titlebar, is your OS based on Menuet?