ScorOS is a project constantly developed in GB Studio. Pushing the boundaries of what can be done, what's possible, and what isn't.
How did the ScorOS Project happen?
ScorOS was birthed into creation back in 2018 - 2019.
I happened to already have knowledge of Operating System creation as I had experience with Assembly language that I wanted to use to make my own OS.
Sometime later I found out about GB Studio, a piece of software dedicated to the cause of GameBoy/GameBoy Color games being created, easily and efficiently. It intrigued me quite much to the point of where I decided to create ScorOS, the first possible every day Operating System that functions on a browser, and in an emulator.
Where did the project go in the last few years?
I took a long hiatus from ScorOS due to personal concerns but, I have recently begun to revamp the entire project, I'm working from the ground up again, to make ScorOS better, to improve upon what I first birthed into the world. There are feats like this done before but...none as grand as what ScorOS is planned to be. ScorOS made considerable progress during it's early life-cycle, but due to circumstances I was unable to recover the files for the original ScorOS project, and instead I lost everything which meant I had to restart.
In the last few years ScorOS has made considerable progress, getting some backbone to the "fanbase". However as I stated, ScorOS is being reworked, for years to come.
How is ScorOS changing from the B-Model?
So, for anyone that doesn't know, ScorOS was working off of something I like to call "B-Model" and what that is, broken down, is essentially a method of creating while learning. So, back in the early stages of ScorOS I was working in the B-Model. So I was learning how to make ScorOS in GB Studio, while making and releasing ScorOS in GB Studio. This time, I have knowledge I didn't have before, not only about programming, but GB Studio, OS's and ScorOS itself.
Due to the nature of requiring to change from the B-Model, I realized that the things ScorOS lacked the most, was unique design, usage-efficiency, and important updates as well as the decision of functions that aren't needed, rather than the functions that are. Making this realization I decided on a few things.
1. Creating a design that doesn't copy other OS designs is going to be one for me. ScorOS had original inspiration from a Fantasy OS known as PixelVision8. In realization of the fact that I was copying some of it, which included the trash bin, and the top bar...it wasn't ScorOS-esque if I may. This time I'm creating a sidebar on the left side, where the applications are in essentially a tube shaped taskbar.
2. Usage-Efficiency is a difficult task to achieve when the only input options you have are 8 keyboard buttons, and shortcuts don't always make it easier, in fact it can make my tasks more difficult, but it also might make yours more difficult as well. For that, I need a solution, so I'm working on a method for streamlining workflow, and so much more as I work on the newest model of ScorOS.
3. Important updates, and functionality. Ah yes, the knowledge really flows here, it's where most of your brain power comes in. Functionality is truly important in an OS, but if there's no functionality there's no Usage-Efficiency, essentially everything depends on functionality, even design, because they go hand in hand.
So functionality will be possibly updated and changed in every update, allowing you all to get the latest, and greatest of ScorOS. Until I release ScorOS v1.0.0 (Update Model: 1C-90555 [Codename: 1Up]), This project will be in it's Beta form, meaning a possibility of unchecked bugs or glitches.
Now speaking of updates, I will now be releasing updates for ScorOS in a proper manner moving forward. I won't be playing around with small updates, such as minor design changes or such anymore. If its a problematic bug, or glitch being fixed then I'll perform a minor update, if there's a big change in functionality, streamline, or efficiency then there will be a proper update.
How did the ScorOS Project happen?
ScorOS was birthed into creation back in 2018 - 2019.
I happened to already have knowledge of Operating System creation as I had experience with Assembly language that I wanted to use to make my own OS.
Sometime later I found out about GB Studio, a piece of software dedicated to the cause of GameBoy/GameBoy Color games being created, easily and efficiently. It intrigued me quite much to the point of where I decided to create ScorOS, the first possible every day Operating System that functions on a browser, and in an emulator.
Where did the project go in the last few years?
I took a long hiatus from ScorOS due to personal concerns but, I have recently begun to revamp the entire project, I'm working from the ground up again, to make ScorOS better, to improve upon what I first birthed into the world. There are feats like this done before but...none as grand as what ScorOS is planned to be. ScorOS made considerable progress during it's early life-cycle, but due to circumstances I was unable to recover the files for the original ScorOS project, and instead I lost everything which meant I had to restart.
In the last few years ScorOS has made considerable progress, getting some backbone to the "fanbase". However as I stated, ScorOS is being reworked, for years to come.
How is ScorOS changing from the B-Model?
So, for anyone that doesn't know, ScorOS was working off of something I like to call "B-Model" and what that is, broken down, is essentially a method of creating while learning. So, back in the early stages of ScorOS I was working in the B-Model. So I was learning how to make ScorOS in GB Studio, while making and releasing ScorOS in GB Studio. This time, I have knowledge I didn't have before, not only about programming, but GB Studio, OS's and ScorOS itself.
Due to the nature of requiring to change from the B-Model, I realized that the things ScorOS lacked the most, was unique design, usage-efficiency, and important updates as well as the decision of functions that aren't needed, rather than the functions that are. Making this realization I decided on a few things.
1. Creating a design that doesn't copy other OS designs is going to be one for me. ScorOS had original inspiration from a Fantasy OS known as PixelVision8. In realization of the fact that I was copying some of it, which included the trash bin, and the top bar...it wasn't ScorOS-esque if I may. This time I'm creating a sidebar on the left side, where the applications are in essentially a tube shaped taskbar.
2. Usage-Efficiency is a difficult task to achieve when the only input options you have are 8 keyboard buttons, and shortcuts don't always make it easier, in fact it can make my tasks more difficult, but it also might make yours more difficult as well. For that, I need a solution, so I'm working on a method for streamlining workflow, and so much more as I work on the newest model of ScorOS.
3. Important updates, and functionality. Ah yes, the knowledge really flows here, it's where most of your brain power comes in. Functionality is truly important in an OS, but if there's no functionality there's no Usage-Efficiency, essentially everything depends on functionality, even design, because they go hand in hand.
So functionality will be possibly updated and changed in every update, allowing you all to get the latest, and greatest of ScorOS. Until I release ScorOS v1.0.0 (Update Model: 1C-90555 [Codename: 1Up]), This project will be in it's Beta form, meaning a possibility of unchecked bugs or glitches.
Now speaking of updates, I will now be releasing updates for ScorOS in a proper manner moving forward. I won't be playing around with small updates, such as minor design changes or such anymore. If its a problematic bug, or glitch being fixed then I'll perform a minor update, if there's a big change in functionality, streamline, or efficiency then there will be a proper update.