Windowing Systems by Example: Introduction

[jojo]

http://www.trackze.ro/windowing-systems ... roduction/

So don't get too excited, this is just the first of a series I'm going to do paralleling the work I've been doing on making mine happen. This post is mostly a ramble on why you would even need to or want to know how to implement a windowing system, which really you guys probably don't need to be told. But if there was one thing I personally have always wished there was more information on, even if it's a bit tangential to the nuts and bolts of an os's core operation, it's os-related graphics programming.

Anyhow, if it sucks, let me know. There'll be a fresh one next week that will actually begin to tackle the subject for real.

[Octacone]

http://www.trackze.ro/windowing-systems-learning-by-example-introduction/

So don't get too excited, this is just the first of a series I'm going to do paralleling the work I've been doing on making mine happen. This post is mostly a ramble on why you would even need to or want to know how to implement a windowing system, which really you guys probably don't need to be told. But if there was one thing I personally have always wished there was more information on, even if it's a bit tangential to the nuts and bolts of an os's core operation, it's os-related graphics programming.

Anyhow, if it sucks, let me know. There'll be a fresh one next week that will actually begin to tackle the subject for real.

It took me quite a while to read all that. Your intro seems to be more about people themselves than the thing you want to code. It is very standard in my opinion, those ground up programmers and library ones. I am very excited to see how your tutorial progresses. I hope to learn something from it. You should post more details about it, for example what languages you want to use, what graphical modes you want, etc... This is a great idea, I don't see many of those tutorials. All doe there is one problem, this forum is full of folks who just started and who are struggling with GDT, Paging, IRQs etc. those internal fundamental features. This tutorial is more likely to help people that have a nice framework that they can use to build their GUI on top of.

[sleephacker]

This tutorial is more likely to help people that have a nice framework that they can use to build their GUI on top of.

Such as me! Well, except the "nice" part.
Just a week ago I started (thinking about how I'm going) to write my GUI, so I'm definitely looking forward to this tutorial series.
Great introduction BTW.

[jojo]

Oh yeah, definitely a ramble and very much about getting some stuff off of my chest as a member of a tiny subculture. The goal there was mostly that I planned to post this in places dedicated more to general programming as well and I wanted to not just deflect the people who might struggle to understand why a person would write a series on such a particular and rarely needed subject but to try and help them understand it, if possible.

Anyhow, I completely understand how this is far from an osdev newbie tutorial since, as mentioned here and in the article itself, there is a lot of groundwork involved in getting to this point. This is more targeted at those who might find themselves in the situation that I did after implementing all of the well-defined technical details and then finding themselves having to go through the process of heading out into the wilderness to actually forge something out of the resources they just built.

And finally, as far as language is concerned, as P5 is written in C and Patch is being written in JS, I will be providing examples in both if for no other justification than I want to show how the same design principles can be reflected in either a bog-standard procedural language and something with more sophisticated support for OO. On top of that, for those who haven't laid the groundwork on their OSes yet, I want them to be able to still be able to play with the concepts by playing around on a canvas.