Omnimaga
Calculator Community => Discontinued => Major Community Projects => KnightOS => Topic started by: Eeems on October 25, 2010, 11:59:36 am
-
ok, I decided to get all my screenshots and progress for my console into one topic :)
(http://img.removedfromgame.com/imgs/1287969704-wabbitemu3.gif)(http://img.removedfromgame.com/imgs/1287975926-wabbitemu4.gif)(http://img.removedfromgame.com/imgs/1287977883-wabbitemu5.gif)(http://img.removedfromgame.com/imgs/1287978904-wabbitemu6.gif)(http://img.removedfromgame.com/imgs/1287980918-wabbitemu8.gif)(http://img.removedfromgame.com/imgs/1287981838-wabbitemu9.gif)(http://img.removedfromgame.com/imgs/1288019884-wabbitemu10.gif)(http://img.removedfromgame.com/imgs/1288022142-wabbitemu11.gif)
Yay! lots of screenshots!
-
It looks great! I thought it was a shot of a huge 384x128 calculator screen, though :D Is Rogue going to be completely console-based?
-
It looks great! I thought it was a shot of a huge 384x128 calculator screen
KOS+Calc2net = win. Actually, THAT would be awesome.
@Deep Thought: I don't think he means the game. Rogue's just the title, right Eeems?
-
Awesome, Eeems!
This is actually running on the current build of KnightOS - there is no difference between it and Rouge.
-
Really nice, Eeems :D
-
Do you have a textroll inside as well? :P
It looks really nice so far! ;)
-
Awesome, Eeems!
This is actually running on the current build of KnightOS - there is no difference between it and Rouge.
but I guess there is a difference between rouge and rogue? :P
-
It looks great! I thought it was a shot of a huge 384x128 calculator screen
KOS+Calc2net = win. Actually, THAT would be awesome.
@Deep Thought: I don't think he means the game. Rogue's just the title, right Eeems?
I know :P I was just wondering if Eeems's OS was completely console based. Answered by SIr.
You made me lose, though >:(
Do you have a textroll inside as well? :P
IT NEEDS ONE
-
KnightOS and Rouge, I mean.
-
Rogue is my version of the OS which is not any different from KnightOS yet, and no I intend to make it x-window's like, with a console though. :)
Getting back to work now :)
-
I assume those different OSes will kinda be like how Linux has different distros, right?
-
Exactly. KnightKernel will be released separately from KnightOS.
-
diversity is a wonderful thing.
-
So true :D
And since it will all have the same Kernel, programs should be able to work on all of them, as long as you have the required lib's and stuff :D
-
Yeah true. As long as it uses the same Kernel, it is nice that there are various OSes to suit everyone's need. People who prefer a command-prompt one might prefer yours, people who always want a GUI may prefer SirCmpwn's and maybe there will be one that looks almost like the TI-86/Casio OSes for those who prefer that style, we never know :P .
-
Well actually mine is going to be windows based, this command line is just me getting some basic stuff made and learning the kernel.
-
Oh ok. Will it still be available in command line too?
/me wonders how small an OS running SirCmpwn Kernel would be if it was all command-based...
-
So basically its like linux for the 83+ 84+?
-
DJ: yeah the command line will be there, maybe not v2.0, but there will be one :p
Broseph Radson: kind of :)
-
will you be able to drag windows? or will they be like tabs, so you can just only switch between them?
-
Most likely switching. Dont know how I'm going to make the interface look exactly yet.
Ok, so I'm having an issue with my LD command, for some reason after converting it over I can't get it to work, here is the code for the LD routine: http://eeems.pastebin.com/8wig6K27 and HEXFromString: http://eeems.pastebin.com/REs3kzL2
It should work, but no hex is loaded for some reason...any ideas?
-
If you do have movable windows you should have a move button that you can toggle so you don't have to grab the title bar. Makes it easier ya know :)
-
well, I think movable window's might be a bad idea, it would be pretty hard to implement.
-
Oh ok. Will it still be available in command line too?
/me wonders how small an OS running SirCmpwn Kernel would be if it was all command-based...
With modifications, you could fit Eeem's entire OS, including my kernel and his terminal, into one page.
-
Movable windows would be inefficient in terms of space. With the other method maybe when you switch from one window to another then the process for the then inactive window could stop or idle until you switch back to it?
Sorry ts kinda hard to explain wut I'm sayin lol
-
I know what you are saying and yes that is kind of the plan on how I want it to work :)
Multitasking is going to be supported so it will already have the framework to do this :)
-
Kk. Don't want to strain that old zilog z8000. He might get grumpy :D
-
(http://img.removedfromgame.com/imgs/1288148225-wabbitemu1.gif)
Just added a small power menu
-
Oh ok. Will it still be available in command line too?
/me wonders how small an OS running SirCmpwn Kernel would be if it was all command-based...
With modifications, you could fit Eeem's entire OS, including my kernel and his terminal, into one page.
Wow O.o. That means we would almost have 2 MB of free archive on a SE calc.
(http://img.removedfromgame.com/imgs/1288148225-wabbitemu1.gif)
Just added a small power menu
Nice :D
-
nice! another question: will this OS be event driven? or will it be the way TiOS is?
-
What does event-driven means? I checked Wikipedia for it, but I still couldn't understand. What would be an example of event-drivenness for a calculator OS that the TI-OS doesn't do?
-
IIRC it's basically allowing programs to be 'notified' of certain events (e.g. file access or link port stuff). I don't know for sure.
-
The GUI will probably be event driven, but I'm not sure about other things.
Event driven means that certain things will happen to trigger 3rd party code to run, if I'm correctly interpreting LordConuptier.
-
Ah so I guess it will be like cron jobs?
-
well, no, not exactly. It's just like Windows. when you click on a Textbox, what you type will appear in that textbox, and when you click somewhere else, that will be activated. It means code is run based on what the user does. In TiOS, when you have to type a name for something, you can just only type a name in the selected input, and you can't select another input. When you want to cancel, you can press clear, but that will bring you back into the main loop of TiOS'es code.
In short:
Event-driven: code is linked to actions of the user.
non-event-driven: code is just build up in simple loops and lusses.
conclusion: Event-driven is much more flexible!
-
Yes, it will be event driven, in that case, at least with GUI.
-
Ah ok I see. That seems better then :D
-
That sounds great! So does that mean we can switch between parts of the OS without canceling each one?
-
Pretty much :)
-
It's already multithreaded - you can run 20 programs at the same time.
-
Ah so you put a cap on the amount you can run :)
-
Yeah, there's only so much room in the thread table.
-
Ah ok I thought so :)
well it's a good idea anyways :)
-
Will one program running by itself be faster than 20, or do you just have free threads left idle?
-
I think it will run faster, but I'm not sure. If I remember, programs that are in the background won't take as much processing power as the main one. Or only some stuff will be ran. SirCmpwn would need to confirm this, but you might be able to find some info in the other threads in the meantime.
-
I'm pretty sure it would be slower with multiple threads. I think someone mentioned that having too many threads would be impractical, so it probably just starts at one thread.
-
It will be slower than multiple threads, yes. However, threads can set an option - FreezeOnIdle. This option means that if the thread does not have focus, it is frozen and no longer executed until it is no longer idle. This is useful for a notepad type of thing. The notepad process would freeze when switched out, and resume when switched in. Programs like Mosaic would be set to remain active on idle while compiling, for example.
-
That's a good idea. Is this already implemented? And what do you mean with this:
It will be slower than multiple threads, yes.
This can be interpreted as an confirmation of Deep Thoughts post, but in content it means something different, the way I read it, could you clarify it pls?
-
It will be slower than multiple threads, yes. However, threads can set an option - FreezeOnIdle. This option means that if the thread does not have focus, it is frozen and no longer executed until it is no longer idle. This is useful for a notepad type of thing. The notepad process would freeze when switched out, and resume when switched in. Programs like Mosaic would be set to remain active on idle while compiling, for example.
Yeah sounds like a cool idea. It would suck if you opened a game then quickly switched to a math program with teacher key or something, but the math stuff ran several times slower :P
-
Well, games would probably want FreezeOnIdle. This would stop them from running when you opened up the math stuff.
-
Well, games would probably want FreezeOnIdle. This would stop them from running when you opened up the math stuff.
Sounds like a really good idea :D
It will be slower than multiple threads, yes. However, threads can set an option - FreezeOnIdle. This option means that if the thread does not have focus, it is frozen and no longer executed until it is no longer idle. This is useful for a notepad type of thing. The notepad process would freeze when switched out, and resume when switched in. Programs like Mosaic would be set to remain active on idle while compiling, for example.
Yeah sounds like a cool idea. It would suck if you opened a game then quickly switched to a math program with teacher key or something, but the math stuff ran several times slower :P
I really hope teachers will allow KnightOS :P
-
Well, games would probably want FreezeOnIdle. This would stop them from running when you opened up the math stuff.
Yeah I meant some sort of pause on them, so they resume when no longer idle.
-
Yeah, that's correct. There will be an event driven system so that programs will know when they are about to be frozen, too, so that they can pause the game or something.