What Order Should I Make Things In?: Difference between revisions

This is a question of style. You can start at the start and dig straight in, writing a bootsector, then a minimal kernel, and build from there. You could skip the bootsector, and use a ready-made bootloader like [[GRUB]]. (Peopleit's keepopen arguingfor ifdiscussion rolling your ownwhether [[DoRolling iYour needOwn toBootloader|rolling writeyour aown bootloader|bootloader]] is a valuable experience or a waste of time).) OrYou youcan canalso write bits and pieces in no specific order, and just put them together at the very end. There is probably no right or wrong way to go about doing it. If you would like an overview of things that are handy to get working (and are practically a must for every OS), you can keep on reading.

# Being able to printPrinting strings and integer numbers (both decimal and hex) toon the screen is certainly is a must at early stage. This is one of most basic ways of debugging, and virtually all of us have gone through a kprint() or kout in version 0.01.

Once those steps are takencompleted, whether you'll try to have a working GUI before you have a filesystem or, multitasking or module-loading facility is '''really'''completely up to you. Try to sketch out what is likely to depend on what, and do things in 'least dependent first' order.

For instance, the GUI could depend on the filesystem to load bitmaps or resources, but you don't necessarily need bitmaps in your very first GUI... Good advice in such a case is to design the interface of the filesystem first (be it open/close/read/write or something else), and then go on with whatever you prefer but, respecting the interface on both sides.

He's been impressed by the "naked beauty" of DOS times. The first thing he wants to be achievedhave is a blinking cursor after a ">" symbol so that he can type commands. No matter if there's no way to start 2two programs at the same time: he just needs a text editor and a FAT12filesystem driver ;).

His test-machine has no keyboard and no screen. No(no one needs that). All he needs is NICs (Network Interface Cards) ... Plentyplenty of NICs... and an Ethernet cable to see if his kernel responds to pings and routes packets correctly. His kernel of course has powerful multithreading and a complete TCP/IP stack, of course.

Look through the window: ... Seesee that background with alpha-blending and mythe anti-aliased fonts ? See the corner of the screen ? That's Klik's Startstart Menumenu! Hmm, no.: I have no so-called 'programs' folder, as iI can't load 'programs'any applications for now, but here's a 16-items list of test cases for my WidgetToolKit.

Works in a darkydark corner of a small room with listings all around. Her system has much evolved since last year, though all she can show you is still the same: bunches of A's and B's displayed in no- obvious- order on a text console and that she controls with magic key comboscombinations. HearYou hear her talking about how she implemented componentscomponent programming, auto-dependencies dependency-resolving and a virtual clock algorithm for her scheduler.