Am I starting to have a bad time? (X5-002.1 (1+2))

[previously] - sigh. So ... I was starting to have a bad time, yea. And ... I'm still shaky. I mean ... I don't know.

But then, as it seems, this thorn has to go out of my paw - I guess I shouldn't be so worried showing off like ... OK ... 18 years worth of dev time. Which is to say, yea, on and off ... it's not like I got paid for it or anything. Or didn't have other things to be concerned about.

So, before I can truly move on into Linux I have to make sure that everything is implemented at base. Possibly. We'll see. Anyway ... that's also where I'm currently at with my code. So ... . I've been urged to start over I guess ... got the hangs of it, and then was asked to start over again. It really did hit a few nerves and stress-factors - but I guess ... it's all for the better.

Within all these attempts I'm currently stuck on the same problem. Well, it's not so much a problem as it is ... a thing I have to fiddle around with until everything is in the right place. The building blocks are mostly there - it's just a matter of ... tieing a clean knot I guess.


And then this and this and that. So ... maybe it'll be fun. I'll give you something defunct, you'll be like "but why" and then I'll be like "OK here" and then you'll go "oh, that's why". But sure. Reflecting over what I'm thinking and doing in a way that forces me to justify myself ... . Well, now that I think about it. A lot of the bunk that I've been producing over the years was kind of ... following a trail of some kind of ... let's call it "user symmetry" - to find some ... middle ground between the weird conventions of my own and "the normal world" - and, yea. Whatever copium I was on last time I wrote of my progress, yea, it's ... way snappier now.

And yea - it's like a Loonie Tunes moment for me, me being like Coyote runnung into an Abrissbirne.
Or Tom just running into something that also is getting at him with high velocity. Something heavy of course. It's Tom.


And yea - it's all there now. Basically I would just wrap it up and then take it back in time, take a tour back through my log and take everything in that I had working then. Maybe I'd just do it all over but I'm sure that some things here and there should have still been worth the time.

By that logic I can give you a little bit of a roadmap:


So, first - the whole reason to this - was the Zero Core. Or so, the System Component along with pseudo Zero and System Cores. The goal here is to simply ... I don't know. Mimic an OS perhaps. It's ... like a mental condition perhaps. I have to have it this way. "Trust Me". It's like ... about the Geometric Alignments of "Code" (Logic). It's Alchemy. It's possibly bogus - if it works it works - but then, that's where all the bells and whistles come from.

The whole thing gets to ... maybe show that off. It's also much simpler than ... I thought. Compared to X4 - yea. It's ... . Let's call it an "Inception Error".

So. Because I really want to dig into it, it might not make sense to try and wait until I have it all fleshed out. But this one thing ... . Well. After that, once the basic framework for getting a project to run and to the screen - I suppose that's when I'll feel fine showing it off. If I'm not getting it done right, I'll show it off anyway and discuss it with you.

Then the very next step would be to work with the Filesystem. So, the project will need a browser - and a way to navigate it. So, that's - maybe ... . So - if we call this break a phase break, because, well, it is - there's just some minor things we'd want to migrate back, but ... so - we'll get to do some geometry with pixels, filesystem stuff, input stuff and drawing stuff. And a final first step towards utility should be a Text Editor.
So, that's all stuff I haven't done yet and would get to do for a first time. I mean - mostly. I've done some minor thing here or there. But nothing that really ... remained.


ZERO CORE implementation: Part One :: System Component

So - the source file we're looking at here is ljack.cpp. LJack is to stand for Lumberjack, with the abbreviations LJ and subsequently LJack entailing Libra as L. Libra is intended to be a language based backbone to the system. That means: To properly interface between a variety of different architectures that each come with their nuances - it is for once advantageous to lean into those nuances and allow them to "be" such that the underlying principles can be employed to their best potential. This however interferes with the next layer. So, the Inception Error occurs as the burden of one layer is shifted on to the next for 'some' reason. In as far as its design doesn't account for that extra burden properly, there's like ... spillage. Logically. It might not matter if it's like a function that isn't used or another function that's being overused in a lot of weird and uncanny ways - where 'low spillage' basically just translates into less jumble ... I suppose.

So, one would "simply add" another layer to the thing that takes up the extra burden, sure - and yea, that's also what we do here. So, Libra is in and of itself "Language Based" in that its design is meant to reflect linguistic logic. So, if I say "Screen" - it linguistically refers to a thing and its capabilities. Internally however it's buffers and strings and numbers and bitmasks and what not. So, for the thing one wants to have comprehended in the term, there's a lot of things that ... come together. Like when there's multiple screens. And so, eventually there's more and more tiny pieces - each with it's own meaning and stuff - and for the system itself a lot of that is yet again somewhat meaningless. So, the system should be static - so, what it needs it could take more directly. And that it does. And what we're looking at there is multilayered.

As - Graphics is just one thing that entails a range of things. And as all that comes down to one point, so or so, other things come down to one point too. And they all come together somewhere, vanish in their origin - and return to zero.


One way to reduce inception errors ... well, I guess you could call it a form of magic or wizardry since there's probably no way to comprehend an intuitive answer. But, here's an attempt: is to "bind things" into desired limits.

Uhm ... we'll get to that. So, [here] the package, which only includes the System Component, thus adding some stuff to crystals.h - and that's also ... already ... this out of the way. The main reason to have it where it is is because it's not technically a part of the system. Also technically it would be part of the 'zero' core, but we don't really need it to be there. But now we have colored output.

And yea. As a disclaimer: I don't really tend to work much "on" these things but I work a lot WITH them. Sortof. So, it's "done and gone" - as ever so often I return back to it. And now is where I'll have to do the part I was previously talking about I guess. Still, perhaps, here in Windows for good measure. Anyway ... I suppose, since I'm ... going to share it, there's not much of a concern there, is there?


So ... then. Or ... ? Hmm. No. OK, so ... Zer... uhm. No.

I mean, it's not just the Zero Core. As said - the whole thing is layered - and ... the thing I need has some depth to it. But I suppose I can take it as far as it goes ... as yea, that's the next step anyway - we'll see. Hmm ...