Ideas for Dex4u

Ideas for Dex4u
What do you all think about making Dex4u work as a single-tasking OS in CLI, but multi-tasking in GUI ?. Note: There will still be a basic form of multi-tasking that will work in GUI or CLI that will be similar to Dos TSR for drivers. This will mean that when you go from GUI to CLI that all pressers will be TERMINATED . I will be back :lol: .

Sounds exactly like f.e. Windows 3.1 and DOS :| In other words, just don't. Just make it or multitasking or monotasking. Don't make a mix. If I'm happen to use an OS, I prefer sometimes the console over the GUI, and it sucks when I can't run multiple programs.. (in the console I use amp, mc and possibly 'links', nmap, etc.) DennisCGc.

Your right there would be very similar :cry:, maybe it not such a good idea . The problem is this, I see Dex4u as a single tasking OS that runs one program very fast, i all ways saw MenuetOS as a desktop OS for ASM programmers like us. But now i see Menuet, not being the Desktop OS i thought it would and us ASM programers need one, linux is fine if your into C programing. So i may add a desktop ver of Dex4u OS, which would be full multi-tasking, along with the single-tasking ver :idea: .

That was just my opinion. :) Maybe you can use a 'switch' (turn multitasking on/off) eg not limiting it to the graphical/text mode. I see your point why a switch has to exist (for your OS), but IMO this shouldn't be limited to the mode where the user is in (text or graphical) DennisCGc. PS. Please keep in mind a multitasking OS works different than a monotasking OS, but I think you already knew that ;)

Maybe i am trying to have the best of both worlds, and i will end up with worst of both :lol: .

Just what I think, If multitasking version and single tasking version are separate then that *might* work. I would probably use the multitasking version. The CLI could bring up a menu of 'sessions' when you press alt-tab (or other hotkey). I'm not sure if thta can be done/ is a good idea. Jas2o

Thanks for all your ideas ,Your ideas will help to shape Dex4u into the OS we want :) .

Opps! I ment to say I would probably use multitasking. Jas2o

I think a single-tasking CLI with the option of running multitasking in CLI mode would be good. That way a beginner programmer learning Assembly can do simple tests and learn, while a normal user can run a multitude of background tasks. Just my 2c :wink: What the...? A well-written OS shouldn't let the programmer notice it's operating in a multitasking environment. If a beginning ASM programmer writes a program in a multitasking environment, it really should be the same way as in a monotasking env. (unless you have thread/fork/etc support in your program, which makes your program a bit more complicated :twisted: ) For gods sake, most OS programmers just don't implement cooperative multitasking anymore. (It ain't the early 1980s) The advantage of having that switch is that a program is able to get 100% of the CPU time for itself. (game, critical nuclear program) But then as well cooperative multitasking can be used (although I don't like cooperative multitasking). But please, don't come with those arguments. Infact, I only can name advantages of having a multitasking environment if your program crashes. (you know, having another console where you can kill/debug/edit/recompile your program) @others: I vote for just a single one with just a 'switch'. Of course the switch will kill all the other programs, which the main program is the only who's running. DennisCGc.

@DennisCGc, You need to chill out a little :wink:. When there is less going on and a single task it easier for a beginner to understand and get the whole Picture. Once you have multi-tasking, memory management and protection etc, it not as easy to understand for a beginner. Thats what solidus117 meant.

@Dex: I am :P But IMHO it just ain't neccesary to have a monotasking OS just for the beginner, because that, implied by solidus117, would ease things a bit. I just don't get that. You could leave the thread/fork/etc shit out of your program and still it would work on your multitasking OS, while it could work on a monotasking OS. It might be a bit easier for other programmers, but I just don't get the whole point. Anyway, if a programmer starts, they just have to 'push the button' :P DennisCGc.

Maybe you should wait with this? I think there is alot of other stuff on the to-do list without having to add multitasking.. :) If you add it, i think it would be better to have two seperate versions instead of adding stuff.

Your right bubach, multi-tasking is at the bottom of the to do list, but even Dos had a simple form of multi-tasking (TSR). Top of list is finish Ed4u off (Dex4u's text editor ) , then port fasm, then add Networking and so on, but i still find coding a OS fun :) .

Dex, if you've ever written network apps on windows you soon realise why ioCompletionPorts and overlapped structures were created. Waiting on IO ports just kills performance, so although I agree with bubach about there being alot of other stuff on the to-do list without having to add multitasking, unless you can come up with a new, better way of doing things, if you're going to add networking, I think you'll find some sort of multitasking is enviable ..... but as with most things, I'm probably wrong :)

View Full Version: Ideas for Dex4u