What does your OS look like? (Screen Shots..)
- DeezRamChips
- Member
- Posts: 132
- Joined: Fri Apr 08, 2016 5:03 am
- Location: atapio.cpp - why won't you work :(
- Contact:
Re: What does your OS look like? (Screen Shots..)
A little update on my os:
My github page: https://github.com/AlexandreRouma
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
- DeezRamChips
- Member
- Posts: 132
- Joined: Fri Apr 08, 2016 5:03 am
- Location: atapio.cpp - why won't you work :(
- Contact:
Re: What does your OS look like? (Screen Shots..)
It supports:
HLines
VLines
Lines
Circles
Bitmaps
Text
rectangle
Filles rectangle
HLines
VLines
Lines
Circles
Bitmaps
Text
rectangle
Filles rectangle
My github page: https://github.com/AlexandreRouma
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Re: What does your OS look like? (Screen Shots..)
Roman wrote:Why don't you just write a bitmap font parser for an existing format?
I don't want to mess around with any of those at the moment. I am only going to use this BIOS font port for my graphical shell. Once I start writing my compositor I'll see what I can port in order to support standard font types. Supporting those without a proper VFS is not an option. Also is it just a coincidence that freetype2 has some "Ghosts"?max wrote:Why not port freetype2? It's much easier than it sounds.Roman wrote:Why don't you just write a bitmap font parser for an existing format?
OS: Basic OS
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
About: 32 Bit Monolithic Kernel Written in C++ and Assembly, Custom FAT 32 Bootloader
Re: What does your OS look like? (Screen Shots..)
I wrote my own TTF parser because I really dont like bloated libs.max wrote:Why not port freetype2? It's much easier than it sounds.Roman wrote:Why don't you just write a bitmap font parser for an existing format?
Its kinda funny that most libs are bigger then my whole OS
Looks great, do you use a double buffer?DeezRamChips wrote:A little update on my os:
Do you support transparency?
- DeezRamChips
- Member
- Posts: 132
- Joined: Fri Apr 08, 2016 5:03 am
- Location: atapio.cpp - why won't you work :(
- Contact:
Re: What does your OS look like? (Screen Shots..)
I don't have transparency yet, I'm havinf trouble making an algorithm :/
And no, I don't use double buffering, still don't have a use for it ^_^
And no, I don't use double buffering, still don't have a use for it ^_^
My github page: https://github.com/AlexandreRouma
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Meme-deving since 420 Bc !
YouTube: https://www.youtube.com/channel/UCyJnOD ... C8Y7pccc6A
Twitter: https://twitter.com/WhatsTheGeekYT
Re: What does your OS look like? (Screen Shots..)
Holy **** ...pdurlej wrote:
Let's put this to my inspirations list.
Asking for a premission : Can I use that menubar above in my OS?
You shall choose a name for your OS.
Take Prisma. It sounds good.
Or you could take, hmmm... Well let's say Endline.
Where's download?
Last edited by Ycep on Wed Aug 24, 2016 7:14 am, edited 1 time in total.
Re: What does your OS look like? (Screen Shots..)
Nameless OS is currently closed-source. I've been thinking about releasing the OS under an open-source license, haven't decided whether to release the source code yet.glauxosdever wrote:I forgot to ask, however, is there some source code and/or disk images to test your OS in a virtual machine?
There is an i386 VM image, http://www.durlej.net/nameless/demo.img.gz:
Code: Select all
gunzip demo.img.gz && qemu -hda disk.img
Re: What does your OS look like? (Screen Shots..)
What do you mean by using the menu bar in your OS? It's just a menu bar with four options.Lukand wrote:Asking for a premission : Can I use that menubar above in my OS?
-
- Member
- Posts: 501
- Joined: Wed Jun 17, 2015 9:40 am
- Libera.chat IRC: glauxosdever
- Location: Athens, Greece
Re: What does your OS look like? (Screen Shots..)
Hi,
I tested the OS. It's a bit shame you don't support 16-color mode, otherwise it would look very similar to Windows NT 4, which I got to test in a virtual machine last year.
However, I by no means expected the filesystem structure would look like from a UNIX system. You would however like to have include and library files installed in standard directories.
I would also advise not having boot and kernel files in /lib. /boot looks like a better choice.
Regards,
glauxosdever
I tested the OS. It's a bit shame you don't support 16-color mode, otherwise it would look very similar to Windows NT 4, which I got to test in a virtual machine last year.
However, I by no means expected the filesystem structure would look like from a UNIX system. You would however like to have include and library files installed in standard directories.
I would also advise not having boot and kernel files in /lib. /boot looks like a better choice.
Regards,
glauxosdever
- BrightLight
- Member
- Posts: 901
- Joined: Sat Dec 27, 2014 9:11 am
- Location: Maadi, Cairo, Egypt
- Contact:
Re: What does your OS look like? (Screen Shots..)
I've tried Nameless OS in QEMU, and I'm surprised that performance is really excellent.
How do you get such good performance without using SSE?
How do you get such good performance without using SSE?
You know your OS is advanced when you stop using the Intel programming guide as a reference.
Re: What does your OS look like? (Screen Shots..)
Nameless OS does suport 16-color mode, see one of my previous posts. There is a separate VGA driver.glauxosdever wrote:I tested the OS. It's a bit shame you don't support 16-color mode
This image does not include the SDK.glauxosdever wrote:You would however like to have include and library files installed in standard directories.
Nope, moving files to /boot would increase complexity with little to no benefit. The sysload boot loader reads, apart from the kernel, several files from /etc, and some devices drivers from /lib/drv.glauxosdever wrote:I would also advise not having boot and kernel files in /lib. /boot looks like a better choice.
Moving the kernel alone to /boot would not be sufficient to allow for booting from /boot, moving more files would make the filesystem hierarchy inconsistent. In Nameless OS system-wide configuration files belong to /etc and device drivers belong to /lib/drv.
This is a design choice. Sometimes worse is better.
Re: What does your OS look like? (Screen Shots..)
If you rename the .img file to .hdd, then VirtualBox will boot as well, but you get an ENODEV error during boot and a kernel panic. Any idea what device it's looking for?
Project: OZone
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Source: GitHub
Current Task: LIB/OBJ file support
"The more they overthink the plumbing, the easier it is to stop up the drain." - Montgomery Scott
Re: What does your OS look like? (Screen Shots..)
By developing the OS on a 200 MHz Pentium machineomarrx024 wrote:I've tried Nameless OS in QEMU, and I'm surprised that performance is really excellent.
How do you get such good performance without using SSE?
If you mean GUI performance, see one of my previous posts for the GUI architecture. The window manager uses a single frame buffer and does clipping to avoid double/tripple bufferring and copying. Buffering is both CPU and memory expensive.
However, screen contents are copied when a window is moved, or a portion of screen is scrolled. This avoids flickering.
Additionally, the both the window manager and the widget library is optimized to avoid painting a single pixel more than once when refreshing the display. Sometimes redraw operations are deferred. Also, the GUI is optimized to only repaint regions that actually need updating. Sometimes several redraw requests of smaller regions are combined into a larger region.
Last edited by pdurlej on Mon Aug 15, 2016 3:22 pm, edited 2 times in total.
Re: What does your OS look like? (Screen Shots..)
Probably the PCI IDE controller. Make sure you have a PCI IDE controller configured (not SATA).SpyderTL wrote:If you rename the .img file to .hdd, then VirtualBox will boot as well, but you get an ENODEV error during boot and a kernel panic. Any idea what device it's looking for?
Re: What does your OS look like? (Screen Shots..)
This thread has gone off-topic a bit, here is another screenshot: