if you were................

If you were to write your own GUI (i don't mean a shell thing) where would you start, what would you include ??

I'd start by making it look like MS Office, including proper File/Edit/Help menus -- key shortcuts as well :) Then dockable, customisable toolbars.

I would start by stealing it from Parksie.. :D

Hehe :D

so you wouldn't worry about drivers or desktop, i would want the desktop to work well

The desktop's part of the shell, and drivers are part of the kernel :confused:

sorry, i meant as a whole

a whole OS?

yeah alright a whole OS, where would you start what would you want in it, what would be your selling points ??

You'd start by learning Assembler.

:)

I would wait for all of you guys to finish and then get the crack for it.

it's not Assembler it's Assembly:rolleyes:

It can be either, depending :)

i know that's why used the rolleyes:)

Oh okay :) I'm just a bit dopey now :D

How about if i use it this way i went to the assembly to learn about assembler.:p

maybe c++ is a better choise

I agree, C/C++ would be a better choice, although ASM would come in useful when you need the speed intensive stuff (Disk I/O, Mem access, drivers).

http://forums.vb-world.net/showthrea...threadid=60459

Try that: There's my O.S.
zmelinz, is that why you started this thread?

But, I'm pretty sure that some of the parts HAVE to be coded in ASM.... like.... well, the C++ interpreter ;)

C++ isn't interpreted...

Oops.... I'm tired today..... I meant the C++ compiler, and the 'interpreter' that does what the .exe file tells it to do........

you could write the compiler in VB if you wanted. It just has to write exe files.

Fair enough...I see what you mean now :)

but, you'd have to write the VB compiler in ASM then.

No, you can buy it from microsoft.

But this isn't Windows.

You don't need to run the compiler on the OS, just create the exe files and the boot disk. you don't need anything on the other computer at all, just your OS.

So long as in your OS you register *.exe files as being executable code, you can compile them in existing compilers. You would only need to write your won compiler in ASM if you were using a CPU with a different instruction set architecture.

I imagine you could create a C/C++ compiler using an existing C/C++ compiler.

You could, and you'd also use tools such as YACC or Bison to create the parser (flex is good too).