But is there a way to make a graphical user interface in assembly? I mean, I wouldn't like my OS to have a text based interface.
Any help anyone? Thanks
Modern boot loaders incorporate many of the fundamental operating system concepts including memory management and drivers; some of which are as complex as little operating systems themselves. It is highly recommended to change this tone if you want to survive in this field.omar wrote:I finally decided to get rid of dealing with stupid bootloaders
Obviously, yes. If it was not possible in assembly language, it certainly would not be possible in higher level languages. Graphical user interfaces however are really complex and are tailored to object oriented design.omar wrote:so I just got GRUB and all is going good. A wrote a hello world kernel in C and it loads and everything is working great.
But is there a way to make a graphical user interface in assembly?
Why not? Providing a text based console is very important and provides scripting functionality and command line tools that are more suitable and simpler to use as back-end tools rather then integrated in a single graphical application.omar wrote:I mean, I wouldn't like my OS to have a text based interface.
If you have to ask, you are not ready. Seriously.omar wrote:Any help anyone? Thanks
I kind of agree with you but, however, I am not so sure why I do that. A text console is something that we take very much for granted. If we made a design decision of not having it, it might help us to come up alternative ideas that may or may not be better. If we still had the text console, we might want to change the very intrinsic features of it, e.g. not allowing a "freely-formatted" input that requires parsing.neon wrote:Why not? Providing a text based console is very important and provides scripting functionality and command line tools that are more suitable and simpler to use as back-end tools rather then integrated in a single graphical application.
In my opinion, users don't want to use the command line at all. What they want is applications and tools with decent/graphical user interfaces, plus the ability to write scripts that control applications and tools.Antti wrote:I kind of agree with you but, however, I am not so sure why I do that. A text console is something that we take very much for granted. If we made a design decision of not having it, it might help us to come up alternative ideas that may or may not be better. If we still had the text console, we might want to change the very intrinsic features of it, e.g. not allowing a "freely-formatted" input that requires parsing.neon wrote:Why not? Providing a text based console is very important and provides scripting functionality and command line tools that are more suitable and simpler to use as back-end tools rather then integrated in a single graphical application.
Another argument against the command line tools is localization. It is almost impossible to have commands, e.g. "copy" or "move", localized. Output messages can be localized but the command names and command line parameters are still English-only.
Yes.bluemoon wrote:The only scenario you want a text-based console is to ssh into remote host, which a graphical (VNC) may just require too much bandwidth.
Take mac for example, most the functionality of the shell can be replaced by node-based automators, you can possibly get rid of the shell and do thing the "GUI" way.