I finally have finished Skip 2.0!
For those of you who are reading this and are like "what the heck is Skip?" It's the programming language I made in Scratch that I wrote my OS - DevOS - in. It's new features are:
-Keyboard input
-equality if statements
-text coloring and sizing
-slightly better code parsing and running system
And the new VM includes:
-Automatic booting (by calling the boot code on a Skip VDisk)
-easily developable Skip VDisks (virtual boot and system file disks)
-A "no boot file" error wich also lets you switch between VDisks
-key commands that will let you, delete the current boot file, the best way to get to the "no boot file" error, show the controls (power, volume, special keys), and show all of your VDisks.
This took me a long time to make, so DevOS 2.0 is not going to come in it's own VM. It will come in a VDisk though, letting you import it into this project and running it natively.
It doesn't work online so you'll have to download it:
Last edited by ScratchReallyROCKS (2010-09-18 11:10:24)
Offline
Harakou wrote:
ScratchReallyROCKS wrote:
Harakou wrote:
YES! Awesome!
![]()
I knew you'd reply!
![]()
'Course I did. I can't wait to see the new DevOS.
It's still in the starting stages now. It may take up to a month! Changing a whole interface isn't easy.
Offline
ScratchReallyROCKS wrote:
Harakou wrote:
ScratchReallyROCKS wrote:
I knew you'd reply!![]()
'Course I did. I can't wait to see the new DevOS.
It's still in the starting stages now. It may take up to a month! Changing a whole interface isn't easy.
No kidding.
Offline
Harakou wrote:
ScratchReallyROCKS wrote:
Harakou wrote:
'Course I did. I can't wait to see the new DevOS.It's still in the starting stages now. It may take up to a month! Changing a whole interface isn't easy.
No kidding.
I finished the VDisk maker if you want to make your own virtual boot disks for the SkipVM.
Offline
Harakou wrote:
So if DevOS is going to be a VDisk, how are we going to write programs for it?
Easy. (I had to think this through before I implemented the VDisk idea) VDisks include only the boot and OS files. These are the files needed to start up. So, when you "insert" the VDisk, it loads it's files into the stored code list, unless they're already there. Apps you write for DevOS are also stored in the stored code list, so they are accessible from any code using the "call" command. That means that when DevOS is booted, it will read from it's system files, but it can call apps from the list. That also means that if you get a new DevOS VDisk to update your old one, your apps will still be there.
Offline
ScratchReallyROCKS wrote:
Harakou wrote:
So if DevOS is going to be a VDisk, how are we going to write programs for it?
Easy. (I had to think this through before I implemented the VDisk idea) VDisks include only the boot and OS files. These are the files needed to start up. So, when you "insert" the VDisk, it loads it's files into the stored code list, unless they're already there. Apps you write for DevOS are also stored in the stored code list, so they are accessible from any code using the "call" command. That means that when DevOS is booted, it will read from it's system files, but it can call apps from the list. That also means that if you get a new DevOS VDisk to update your old one, your apps will still be there.
Oh, I see. Makes sense.
Offline
Harakou wrote:
ScratchReallyROCKS wrote:
Harakou wrote:
So if DevOS is going to be a VDisk, how are we going to write programs for it?
Easy. (I had to think this through before I implemented the VDisk idea) VDisks include only the boot and OS files. These are the files needed to start up. So, when you "insert" the VDisk, it loads it's files into the stored code list, unless they're already there. Apps you write for DevOS are also stored in the stored code list, so they are accessible from any code using the "call" command. That means that when DevOS is booted, it will read from it's system files, but it can call apps from the list. That also means that if you get a new DevOS VDisk to update your old one, your apps will still be there.
Oh, I see. Makes sense.
And another great thing about this is that people can share their app on VDisks, and people can load them into the VM.
Offline
ScratchReallyROCKS wrote:
Harakou wrote:
ScratchReallyROCKS wrote:
Easy. (I had to think this through before I implemented the VDisk idea) VDisks include only the boot and OS files. These are the files needed to start up. So, when you "insert" the VDisk, it loads it's files into the stored code list, unless they're already there. Apps you write for DevOS are also stored in the stored code list, so they are accessible from any code using the "call" command. That means that when DevOS is booted, it will read from it's system files, but it can call apps from the list. That also means that if you get a new DevOS VDisk to update your old one, your apps will still be there.Oh, I see. Makes sense.
And another great thing about this is that people can share their app on VDisks, and people can load them into the VM.
That's the issue I was thinking of. Apps for DevOS would require a different format, because they would run inside the DevOS VDisk, not the Skip VM.
Offline
Harakou wrote:
ScratchReallyROCKS wrote:
Harakou wrote:
Oh, I see. Makes sense.And another great thing about this is that people can share their app on VDisks, and people can load them into the VM.
That's the issue I was thinking of. Apps for DevOS would require a different format, because they would run inside the DevOS VDisk, not the Skip VM.
What you would do is boot off of the app install disk, which would add that app to the stored code, then the app install disk's boot code would call DevOS, and you would be able to use that app.
You'll see when it comes out.
Offline
Is this the next Dev. OS forum?, because I can't find the old one.
bump#3
Offline
laurence12345 wrote:
Is this the next Dev. OS forum?, because I can't find the old one.
bump#3
No, this is kind of the Advertisement forum.
Offline
Bump#6
Bump#7
Bump#8
Bump#9
Bump#10
I'm very bruised now.
Offline
ScratchReallyROCKS wrote:
laurence12345 wrote:
I'm very bruised now.
![]()
So is the topic XD
lol.
Offline