Getting ready ...

So, this is it then - I assume. ...

Right now I'm being lazy. These articles/files don't have any decoration or consideration for format whatsoever. Sometimes they did. Right now I'm just being honest, ... that I haven't gotten any 'style' per se that I felt comfortable with. On the long run. And that comes in hand with a lack of vision.

So, without vision no layout that works - and yet, I always had 'some idea'. I was thinking, back in the day, to build something I called "Tetrix", next to some other ideas for how to construct my site. What I ended up with is however more something like a 'pale shadow', and that because I had to make up my own stuff where I lacked the vision. So I'm assuming my way into things, well, based on ... what visions guide me.


Now I'm having flashbacks. And vividly enough, ... we've been playing (My brother and a friend [#contemporary (a)]) 7 days to die, ... and something told me to quit playing it. On the other end I couldn't 'stop' playing it, ... as sometimes its just the best thing to do. Playing some game. With friends. One guy is one of the kind that plays Diablo a lot, so, grinding for hours 'as' fun. So, thats the game there. I have trouble keeping up with him. So - it seemed important that I stopped though.
Yet, ... within the extremes there margins. If there were just two things in existence, so the idea, I mean ... between two extremes there is that in-between, and if its 'void', then the extremes themself are 'layered' towards a boundary. And in this sense a thinking in ways of right and wrong (binary) is flawed. Usually the extremes we are able to describe are either too vague or missing something.
So, tomorrow at evening I'll be back off ... enjoying my leisure. But were I playing right now, ... this wouldn't have come together.

These flashbacks pivotally spin around the 'Tetrix'. Along with it I had a vision of what my Desk should look like. I mean, the place where I lived. I had my Netbook and got fancies what to do with it. And yet I had the feeling that there should be some other Laptop on which I ... . Ironically I can now tell that a lot of my 'fantasies' revolved around that machine, which so would happen to be this one. At any rate do things logically carry over, ... as unfolding that way, naturally. As it was, kindof, with the other 2 Laptops I owned. Both Lenovo. One was still an IBM. Anyhow. What this little baby here has is a better form and weight factor. I basically chose it because it had the best 'on board' typing experience. Which makes the list after being told that the best possible performance isn't important. It has to be sufficient.
It was a present from family. I had a budget, ... and my choice with it, plus time to think about it.



I also have to finally however also come to positively speak about Windows. Well, when it gets to building the Tetrix, I somehow, ... automatically slipped into it. Well, being high right now might have helped too. Anyhow.
So, my 'Vision' at base here is this Tetrix thing, which I'm compelled to build and also finally write about. That is - ordinarily I focus around some order or structure, ... regarding how I construct my stuff. "This is for this and that is for that". And sometimes I came around sharing stuff, but that more like as being forced to show a bit of the stuff that I do.
Now the thing is that there are reasons that I feel compelled to write about. They urge forward and drop into ... my mouth, basically.



On the other hand are there also things where I want to go with my website. And all in all, this journey started quite some time ago. When it gets to Linux I certainly was a noob back in the day. Since then I've come to try several things, ... and of these made experiences now ... I can now all in all benefit.
The "main course" this time around is however something independent to the Tetrix. That is the issue that came forward. It hints towards something which I back in the day already had in mind - while the Operating System I'm using now (Windows 10) is in that regard the 'expected' consequence of my leakage. I didn't see that coming!
At least is there a degree of improvements that I can appreciate - while certainly the way it handles hardware is ... well seasoned. Which also gives Hardware designers the 'evolved benefit' of working with a healthy ecosystem.

To bypass security issues I'll just share my work online; And if that doesn't get through, I assume something is wrong. I however have little choice in that matter.
I assume.


So, lets begin. Or do I have anything left to add?
Security. Well. For that I still have my other baby. Obviously, ... one can only have one main computer. Right? Well, no! That is one of those issues. The clutter with them many things. Some people only need a phone. Other people need more. Obviously 'Tech' is nowadays one of our fundamental assets. Its an inevitability. The moment humans arose, tech was a part of us. We grew as a species and thus grew our Tech. Tech is the way we co-exist with the reality around us.
What you wear is the product of it. Even the most simplest of garments is however based on some 'Tech' in that regard. Thats the point.

Even the Bible reflects on it. When the angels descended from heaven, they gave people technology. Or was that some weird Apokrypha? Shiit.


Now, the freedom I can have with this machine is thereby the essential thing. Our ability to 'access' the functions of our computer ... to the fullest of our hearts contempt. Or in other words saying: Not Apple. Sorry. Just for this purposes. We want to evolve - as a whole - and the freedom I have to as a matter of fact contribute to that is an essential part to this working.

... I feels like - I want to dabble in the old for a bit longer.



That is to say: The Tetrix, what is it? Well, it is a Windows-Linux-Crystals computer, where the 'fourth' implied element is ... well, I have to make something up: The Crystals Meta. It is what combines the three. Or Crystals as within Windows and Linux.
I wasn't sure about what to do with this Machine yet. Prior to the "zip-ding" I was already paranoid. Wondering at all whether or not I should "main" the older one. Which makes little sense. So I have to trust this. But ... what for? Or how? What am I going to do?
Meanwhile I had already built something of a file infrastructure, just so to get ready for ... some action. That was strongly driven by an awareness for how messed up things can get with unclean planning. But, how to protect against the unknown? So I had some "tingeling sensations" reminding me of things that didn't work - while so going along - and, all in all this machine is basically still a virgin. Except for the 2017 index.html all the other files I have on this computer are either from store or the internet. So, there's pretty much nothing except some initial traces of usage and the initial setup.

And by setup I mean: Installing the needed/wanted software and fetching some more wanted stuff, like, ... I had some wiki pages printed for some odd reason and so I disposed of that heap after acquiring some 'base Library' of sorts.


And this is phase 1 I suppose. Getting along with the machine.

I was 'told' to get me a Convertable.
So I'm using an Acer Spin 5, with an 8th Gen i7, 8 gigs of RAM, 512 gigs of space and a 640 HD graphics card.


And meanwhile I learn what it means to properly work with the Testimony. The 'spirit input'. Which may happen to be a Unification upgrade.
I don't know. []
The trick is to 'want' what you want to do - so, focussing on your motivation, that what you are concerned about. That way the 'yes/no' thing will have a clearer impact. Its so the 'correct' way of doing things - to rule out some fundamental aspect of confusion to the exact response. So, what the answer relates to. Sometimes its complicated - and then that is that. So - to start with: Partitioning. I was first worried that the way I'm using this machine is flawed, ... that if I don't have a secondary partition I might end up loosing data.

So, one up for windows nowadays is 'start - type in stuff'. It is more convenient than linux unless using something like kuake/yakuake. (???) Or some other way of a single key command line activation.

Sounds nifty, but one thing with Linux is, ... nothing I ever tried there seemed to work out for me. And with this machine I don't feel confident about Linux either. Eventually I might come to just "be done" going back and forth, ... but, well, if Windows one day might not do anymore I'll replace it. Anyhow thats a question. What and why.

Dual booting is cool, but ... whats the point? One generally gets stuck with the one or the other, ... while within Tetrix design terms it is merely there to install Crystals. And that right now isn't a thing, ... with this thing. So, maybe the hardware I should actually be writing about is an Acer Aspire One (Netbook) with 256 gigs of space. Thats where I would start with actually installing a homebrew OS ... I think ... ? Not sure - well. Right now there is only one thing that I take as certain: I'll probably give it a fresh start.
And for 'design purposes' it is the 'backup'. Well.

Yea, final piece 'of the puzzle?': Part of the Tetrix vision was some idea of how useful it might be. Well, taking it as a "this for that" type of thing. What is it that I want? Or need? Questions I had no answers for.
It seems to tightly align to the "I don't trust Microsoft" idea though, that I am not going to get any proper use out of it unless I record my progress. If its going to be 'it' - I might as well ... sortof?

Well - its uncertain - so lets come to that which matters.


The first thing we need is [C:\Meta]. It happens to be available - and with this machine it so stands that the recovery image is on C as well. Its all on there. Meta is to establish for us 'something new'. The general idea is: away from corporate mechanisms. We want something new, for the future; And maybe it is only with trust in God that such an endeavor works out. Or help, however. Its 'dreamy' in the way that just 'saying' it won't make it. But: One thing is clear: For it to be an open base, one must assume some public interest. So, there is one thing people must be aware of, ... its what we're speaking about, ... 'the root'.

So, I was about to add a secondary partition, but ... I'm not sure if I wanted it and the testimony didn't give me a clear answer but finalized on 'not' doing so. I thought more carefully about it, then 'tried' to at least make the default partition smaller (down to about 250 gigs, as small as possible; Which is good - I guess. That it has only 50 gigs on it but some files stored so far back that it forces the default partition to be of that size. Bug or Feature?)


Within Meta there is:

and that as this has always been stuck with me. Never quite right though. I always had some form of it - but this is the first 'all in one' thing that matters. Now, system contains 'download' - and that folder is for everything you download and install. If we're going to add partitions we want to access from within windows, we'll also mount them to folders within system. So - windows can do that now!
We would first want a partition where we'll later have linux. We can there even go and hide it. Like any partition can easily be hidden and unhidden. That is like Linux with gparted. Which app is better? Well, Windows doesn't seem to care at all and just does things. gparted ... without a lot of the gadgetry and not unix-ishly complicated.
While in Linux I wouldn't care about it, I wouldn't install gparted. And now windows has what it was begging for. Good!


alpha is our 'bridge', which is to say: "the hidden root of the system". Or 'dedicated' root. Not 'hidden per se'. Just, the type of stuff it is used for is different to the type of stuff ... that 'clutters around'. And to avoid clutter I first of all decided to just make the primary partition as small as possible. Or, if its different to you, half the available size. It is the 'home of windows' ... and ... 250 is enough to use it as intended, effectively.
I rather not partition anything though. Still a thing. Thus I didn't add any partitions yet. I don't need them either. I have 230 gigs 'void' - and can add partitions when needed, as, 250 yet there are on the other end.

So, as what I use alpha for is possibly still a mystery, ... it is where I in my mind need to have all that is relevant for me when it gets to terms of 'building'. Thats where the source-code for Crystals is going to be, where I'll have my game project; And thus far next to crystals and moa1 there is a 'datavault' folder. That is "Sub alpha" - err, ... there is the 'access side' (short path) and 'datavault' as 'inner space' - thus, minus the clutter. This is where clutter is meant to occur, basically. Thus, the next logical step is to add them to the quick-access thing, ... which Windows can do too ... while, we have to live with the fact that we won't be able to use dolphin here. Which may be a good thing.
Anyhow, we might not need alpha in Quick Access.

That we don't have to deal with the linux root is certainly the big plus here. Which leads me to gamma. Gamma is for the individual to think "My Space" ... minus all the clutter. So, if you think of a landscape, there is clutter round about what goes into that landscape, or whatever might be supported by that which generates it. So, like alpha. If gamma is your space and you have a computer in there, ... it can make reference to alpha. Taking it from there. But we would rather think about epsilon there. Epsilon is meant as 'symbol' for peripheral storage. So - its the "dock" - in a sense - whereby you have stuff that basically exists in entanglement with stuff on other machines. It is the 'you' on a foreign computer basically, where 'your epsilon' is that "of your storage device". An outdated think? Well - its, ... non functional yet anyhow.


Did I mention that I'm high going into this? Its one more thing. I generally have experiences of failure. While being high is the source for most of what I consider progress, none of that has ended well so far.

So, where is this getting perverted? The starting point now is that I have some old computer and and two hard-drives filled with stuff. That is my 'baggage'. Like, why wouldn't I want to have all seasons of Married with Children somewhere?
But do I need it on my computer?

"Back in the day" the Internet wasn't all so common, ... and having it is having it.
For maybe never to be of relevance.


Well, I don't have any code ready by now. I have some code I want to copy here to begin working with it - but before I get there ... this miniscule amount of something is 'everything'.

So are alpha to epsilon just placeholders in a sense that we can yet work with them. The content of Meta is abstract at this point with system already being appropriated setting a tone. The main design philosophy is that its going to connect with Crystals and with Crystals we're thinking of that Operating System we want to step into the future with. So, you'd do well stickening to your own preferences when it gets to a setup. Thats where epsilon starts to get more weight.

Well, the main idea for alpha is that it is where you have your computers main storage. So, when you say you put stuff on your computer, so to your head, you need a place to put it. That is alpha. Or alpha/datavault. So that within alpha you can maintain something like a clean root. Which is - when we get to linux, even if we can't access the Linux root from within windows, we must think of the partition to host a unix root. That is, an array of folders. Folders that 'define' what type of stuff you cognitively associate to 'the root' - and where you want to have your 'stuff' is entirely left up to you. So we can think of /windows as a folder to mount C onto. Then we can create a link to /windows/Meta to /meta. The 'user experience' we want is to however get rid of as much clutter as possible. And so right now I'm also holding back on transferring any data to this computer.


Yet, we need to get started somehow. While windows has several default categories for stuff, we don't really want to use them at this point. If we have pictures of family or wallpapers, ... stuff that 'gels' with the windows experience ... which is at this point rather just window dressing (lol). Which is ... cool!
So for downloads. Downloads is OK, ... but ... eventually stuff just piles up in there. Depends. Its a valuable asset, but for moving stuff out of the way, ... there is 'beta'. 'Beta' from within Crystals is the designated download folder. A flawed concept it seems. The general idea is that when online, the computer could enter a mode whereby only beta is accessible to any process. Then you go 'offline' and where do you put that stuff that you want to exclude from that? By contemporary logic that solicits the idea of using a folder such as 'datavault' to have this 'volatile area' separated from the 'hub'. 'transfer' sounds right. But right now there isn't any need for it. And Crystals here only begins to make sense whence it has NTFS support on board.

Gamma is 'user space'. So, each registered user on a machine gets one. But it is designated user space.

Well - its ... 'strange'. How I get to this. I guess its relevant to ... stick to how things matter, ... and in my vision, ... gamma is this 'empty space' - where, if you open it you can get that 'aaaah' feeling of personal space. As bound to a system. Here we can be paranoid, but if there is one system we trust, ... we use its alpha; However - we so can generate our own gamma. It feels right to so just 'give it' the remaining space on the hard-drive, ... so, 250:34:rest ..., as the images go, ... and have 'rest' be gamma, but ... then ... we get filesystem trouble. I get it.

So, no to that.


Not right now anyway.

So, what do we want? We want 'bang for the buck' ... right?

So, there is wisdom to what you should get. And wisdom to 'what' you get. So, using the stylus for instance ... its best taken as a more precise finger for the touch-screen. As something more like "why it has a touch screen". Although in cases ... it might be handy to have one.

And yea, the only windows folder I really have a use for is the 'Documents' folder. That is where my downloaded files go, those I want to keep in some order.
Like, howto's to look stuff up I might need, an ASCII table, ... wiki pages, pictures of earth ... as document rather than gallery item.

Wallpapers in Pictures works for me.



This machine so far works fine with me. Its comfortable to have in my lap, comfortable to type on - and the stylus is basically more convenient than a mouse, ... in this situation. The convertible function is just a nice extra. It isn't really 'recommended' I assume since once in 'tablet form' the keyboard is exposed. So, maybe there is some trick to wrapping it up in something, ... but thats sortof ... I don't know if it'll ever be useful.

Its kindof heavy. The trackpad isn't really ideal, ... the sound, ... well, ... its OK. Its nothing amazing.


So, what I will use it for is ... 'ironically' ... to 'convert' it into something new. Something that therefore sortof serves as a workstation and a rough blueprint that can be copied; And eventually expanded upon. We'll see how that comes together.

(Yeayea, I don't have any Java, but I rather not overcomplicate my effort. I barely know my way around blender. Enough to create simple .obj files. Its a Tetrix, not a quadruplex.)

Well - apology.
Hmm ... . So, the thing in the top-right is 'MinGW w64', which is what I'll be using to do the first steps. I still need to download NASM, ... and probably win-amp. VLC is regarded as untrustworthy?
Strange.

Sticky Notes. Cool.


Or well, it is a link to a '.bat' file that starts the normal command shell of windows whilst enabling mingw binaries and suggesting some jump to some location. So, we can set ourselves right into alpha. Or alpha/crystals/...whatever.

The main purpose of this excercise is to give you software that allows you to read files that I create, which will culminate into something like a book. A presentation. So - if you are concerned of the 'health' of my working you'll need to keep an eye out for some 'Sequencer' software. Its basically the 'spine' to a 4D data environment. Hereby the 'root' hierarchy of any 'multimedia package' is internally approached as a 4D thing. So, think of an assembly plan to put a table together, ... where there are components (simple 3D structures) and a sequence of things that further may culminate into individual components going forward. With this datastructure in the back it is the goal to provide a 'text-stream' ... with multi-media references and interactive content. Well ... I rather not try to explain it. To follow my passion, that for writing stuff about God, I first need to accomplish this. It is a part of the journey.

And the further usage of it is to start playing with it. So, what I can do, you can do. And with it you'll so get the 'starting package' forward into Crystals. So, and for the start that gets us to the 'main dish', ... the 'raw' Crystals experience as Desktop (Windows/Linux) application. So, as ... interface to start doctoring around with the binaries.

Same ol' claim.

Well, back then the 'first' step to get started with 'the Tetrix' was to wipe the computer and install Zen Linux, ... the 'commandline only' version and start playing around. Now, ... it makes sense.



This will however be no easy "drop in" assembly. I have some code prepared that will help kickstart certain things, but I want to work 'slowly' towards it. I don't want to right away use it to all of that potential. That'd be ... silly.
And so a part of this is going to be the discussion of what code to implement, which then also takes me further into explaining some of the old stuff I get to think about when relevant and ... so. Perhaps I should re-open that book as well. To really be absolutely on the safe side. But, I think not. Things will have to evolve, ... so, ... we might at first need some 'version logic'.
I don't know how to go about this. I mean - setting aside time to code is one thing, ... writting this meanwhile is another. And somehow I have to make the two come together.


But we can't get it done all at once anyway. So - the 'next' step is going to be to get some general coding done, ... setting up MinGW ... getting some initial files ready ... and getting on with the show.


So, what is left to discuss?



in Summary:

There is this thing called Tetrix, which I barely understand yet. It also 'sticks' to some sense of what I should do with this homepage of mine, ... - and I only get a meaning out of this computer by following up. "If you built it, he will come!"?

So, with no code yet, all we have is that filesystem - and dreams. What I can dream up is what I can aim for - and having dreamed tall I know some of the pitfalls that come along. So, I might as well, another time try. Being so however more cautious about what I then actually commit to, while, in some way ... fate may guide us.

Like so, initially there is this "cursed word" Terminal. It "clogs" my mind whenever I try to get started, shoving itself in there as "me first". But do I use ncurses? Or stick to openGL? Or ... 'CrystalsGL' sotospeak. Well yea, that makes sense. But first I have to get me a working prototype. Prior to that we're basically either committing to ncurses and thus not getting CrystalsGL down in time, or simple commandline output. And as that is now so an option, ... we can start to think about where we can go within these conditions. That however was where I previously left off.

That isn't to say that I don't have a working GL environment. It is only that there has to be sense before using it. And so is the Terminal the simple practice of getting one 'raw' aspect of the whole together. A graphical shell with access to whatever is supported there. In the end ... so the concept ... we would want a crystals.dll running in the background as 'personalized' thing, ... which is basically just inception, if you want it that way. Alongside we have an mcore.dll which determines graphical stuff, ... maybe.

So, thats the issue. How to set things up. It seems there has to be that third something - but it isn't graphics, it rather is the core itself. So, one stage further down the rabbithole in regards to how everything works. The 'M-Core'.

But now, what is Terminal supposed to do? Commandline stuff. OK ... then we need an interface wherein we first use stdio?


Neither of that. Well yes - but ... in terms of a 'log' function. Well, the function is the same. Simple outputs. "One liners".

So we might start reading our own script. Starting with parsing. So, we could ... well. So ... the vision dictates that I be going and start with "it". Before we get into parsing, ... and a lot of other stuff, ... also commandline functionality, ... we need "it". "it" ... is something I tried and tried to build, ... sometimes I thought I had a tangible idea, ... but then again, ... I could not quite reach them.

moving forward.


And this is where it might get pervy
//2017.12.11|02:13 | 23:41//

Now, the issue stands that upon writing some more I wasn't confident in this anymore. I had an idea, and ... it turned out that while looking the right way, I wasn't looking at the right thing. However, ... yet it stands that prior to me writing any code I got to somehow announce that it is coming. Else if I just had it now, ... and showed it to you, ... I get the ...feeps... that its gonna be some "I got it from them" kindof thing.

So I got to tell you what I'm planning to do - ... or I'll just write about what I have already. I could do that too. So, first coding then ... writing on it.
Well - as it stands I'm going to report on what I do to this Computer, ... and right now you can see up on top what software I have installed. So, getting to MinGW, ... w64, I installed it to C:\MinGW\w64. Then I'm going to use Sublime for coding, Kate for managing code and Notepad++ for this.



- Now, ... as for what I'm going to do:

There is "this thing" - which as previously lined out will play a part in future things. One example is that the 'filesystem' can be understood as a class. It has elements containing storage devices which further possibly contain partitions. If we want to, we can turn the folder-within-folder thing into a standard. So, path/to/folder1/folder2 registers folder2 as folder1, where from this perspective folder1 is the subfolder. From this perspective 'folder1' is also as far as it goes into that direction. Its the end. The things within folder1 are thereby essentially 'alternate alphas'.

Like parallel dimensions.

Lets call it a ... texel.

If we wanted to be 100% on this we would need a file to determine that 'datavault' is alphas ... default access. What comes to me is calling it an 'alias', determined by a _. prefix. [_.datavault]. In the idea we can further have many of those, while then we might want some index. Or we code conditions into the aliases, while thereby having a conflict which would require us to internally target a specific alias to draw from.

Further: alpha and beta aren't meant to be partitions. Gamma are perhaps something of that kind, ... while epsilon is perfectly abstract. Well, we'll still need a meta folder within Meta. Meta as texel?

No! We will avoid having meta in meta. Here we can use the system folder, while the term 'meta' in regards of filesystem issues is for me reserved to be the 'system root' within the final operating system, and is practically the ... most significant space on the Systems hard-drives as far as Crystals is concerned. It is thereby 'the other end' to the boot being publically accessible - when thinking of the storage device as externalized. There is that type of access, which doesn't bother me too much right now, ... and the 'from within the running system' type of access which is really where software security is important.

What I may not be able to do is to accomplish this much as for a real OS, ... but the datatypes and their logic can be created without any of that. They can be put to work, ... .

So, anyhow. 'Browsing' from the software-design perspective is generally ... when moving up from the simple "I know where to go" type of access a matter of folder indexing. Hereby one thing is that we use the respective functions to read the contents of a folder to something. And because thats how it is, ... there is a specific logic to the filesystem features. SO - while having this theoretical datatree in the background, we can't assume that we can use it for everything except we assume that everything can come as its own thing. Well, naturally. "duh"

So I guess I can publish this now and ... get it done. Or should I stack up for more?


Well, maybe, ... maybe not. Well, "there" I have a vision. Or 'the vision'. And on further inspection I get from it ... what I got to be looking for. Its ... weird to explain. It iterates on my given concerns and adds context to it so I can see which parts of my thoughts are relevant going forward.

So, what I 'have' inside of Epsilon is data.Home, data.Stash and data.Volume. {Anything beyond this is basically irrelevant.} Within data.Home I have what I ... 'get to have' - so as part of the Crystals 'root' experience. Well, ... turns out - thats not the best way to describe it. But what you 'got' is that ... well, we can say that the closer we move to epsilon, the more we need to think in ways of 'timelessness'. Is it good or bad to have it? Is it just there for perverts? Well - and so on and so on. If we want to take it to that, we can here say we have a 'public claim' and thereby then generalize a form, ... so, ... at least speaking of the official stuff. Private things. Semi-official stuff. Whatever. So, do/would I now get to speak of "the 4 pillars". They are basically what make up what I think of what the 'thing I'm working on' should be; And well, on further analysis I might here come to improve on my internalized understanding.

There is a lot of 'blah' here - but it is always a good idea to somehow 'scope out' what the whole thing is to look like.
Well, it is safe to say that once we have the filesystem 'read' in, we want more. And then we might have to break what we have built ... because not enough thought went into it. Yet, ... for me ... With this there are two sides of the story. What I have to do at the 'basis' of everything - what the 'foundation' for this to happen looks like that is; And this part.

So - we can go and just malloc and free some memory in 'main'. Maybe thats what I'll do. On the other side have I done some work previously, ... while I'll possibly start all over. By that I mean ... the basic mechanisms at startup, how much memory goes where ... setting up the general structure.


This structure is also part of the general work. So, "it" is only there to ... make it work. But maybe "it" is to be there first of all. It makes sense. Thinking of it, so, ... we take class "something" and make it a root index. We give it some memory and then call an init function that then appends to the given structure itself.

It sounds nifty, but ... looking at the other side, ... there are restrictions.
It may seem silly - maybe I got to discard the idea altogether though - ... so ...


What I have done so far is ... trying to find the proper way ... in. So far it would happen that the first Application that uses crystals.dll could - if there is such a thing as 'static libraries' - or what its called - run as host application. So, each process that uses crystals.dll thereafter is tied into the same structure. So, that is one thing that now just got a little bit clearer to me.

But so, ... we don't need that, yet. So the idea. Then, first things first.

We then so still have the 'main process' - which now can acquire memory on its own. Technically. Hmm ... so, how do we want it? Do we want to settle for disallowing a crystals app to acquire its own memory? So, requiring crystals to run?

OK - so - whats up?


Disregarding that ... the main focus is on "that which is it". Which I will probably get to 'in depth' while working on it. What I here want is to project what it will do. Or what it will have to do. That were something like a first step. And that as working in tandem with ... the other side. It is something that is ... fair and simple.

Hmm ... so - ... no more ... just quiet?



To speak of some of the more advanced functions. So - 'personal computing' ... what is it? When we look ahead into star trek, we can find some of the benefits of a 'socialistic society' - as there also the general availability of personal information. The idea is that technology enables us to do things. Thinking of clarity ... I have the ambition to be able to map things out. And so moving on there is this 4D thing ... which I was writing about ... and all in all - the two have to work together.

Well - we now do have something called Texels. We do here however not want to bluntly read Meta into a list - each Texel has its individual purpose.
The point is that for the purposes of Crystals we design the system from an independent position. We have a filesystem, but generally it are specific purposes that matter. So the idea however. So there is alpha. But, what if I want to protect certain things? Masking them away? Or making them available ... ..............

Wow - ... what a confusing mess. Well yea, but thats how it is. Things just ... grow. But somehow there is a ... thing ... that holds it all together.

So, ... the idea is to have a thing where we can easily add stuff to. So, something will need to have it - along having some memory to do so. That thing itself is at first sight a 'list'. That list is then created to be used - and the process using it will have to know what to do with the stuff that is in it. If we are reading from a filesystem however, there is additional information that is structurally integral to the purposeful usage of that given data. So - the packages come with a given fingerprint. Hmm ... why did I? The thing is that the process passes that list to a subroutine which is to fill it with a specific type of components. So the list itself would at first only be a simple string. The name of a given element. Easier even: The amount of files and folders. As one thing.

Then there is the logic behind getting the data. What does the subroutine work with in order to obtain it? In simplicity it would work within the confines of the running process. What we can do with a dependency on crystals.dll is to implement a sense of hierarchy.


Well, 4 pillars. The one thing is 'the lounge'. This is the 'setup' the computer is used in publically, in a semi-private manner. Well private. For the matter of being anything here a computer is generally a neutral asset. What then matters is its application as desktop. Then there is 'the archive'. It is one other thing one might want to use a computer for - and here the computer is generally more accessible from within. I guess. That would destinguish it is an independent thing. Or so - the general 'archivation' side should be generally ... like that. Clean.

The other two are 'the mansion' and 'the lagoon'. The mansion is basically the extent of what the system can do turned into something, while 'the lagoon' is now what 'personal computing' is furthermore about.

So, that is what you can do with yourself once you have a computer ... that allows you to expand 'in it'.

But where to put it?


For this we need to have userspace and the applications ... respectively. So, ... what we will do, will yet be able to rely on what we do prior. And so "it" is finally ... something that has to work with 'the lagoon'.

Well - what this is about is ... there are a few things that however happened. So, as safe as it gets might be a flash drive in conjunction with a safe computer. But, ... there are now those things that matter to you - and ... how can I ...?
Ultimately, think of everything as of a map. If we think of something, ... we could call it something and associate text, pictures and 3D models to it. But thats not how a filesystem works.

So the main focus is still on the side of what the things are that are adding to the datatree.


Hmm ... - well. The mistake for me was to get into it making a tour around me. What I instead get to focus on is to say "lets say it is gamma".

So, gamma is empty space, right? Well, not exactly, ... anymore. If it has to be a Texel, we need something in there. I have it with the '__' folder. I don't know. It never really. But in this case, it just looks clean. Lets call it main_access though - and have a fresh empty thing. The start to our Multiverse. So, lets make it up to ourselves - where for demo purposes lets say 'mansion'. Now, it was the idea with __ that it means as much as 'global index'. So, if we want anything to be true throughout the different universes - thinking of the texel as virtual space - it goes in there. But this is then only 'cool' when using the appropriate software for it.

So, ... the idea is that we ultimately want to work with what these things 'mean'. And that might in the end be a 3D Environment. Which in the filesystem might even just be a single file. Associated to some game.
Hereby the idea is, ... well ... I guess what matters is what the system 'will be able to do'.

Clear is that lists may contain lists, ... and if we move on up, and wrap lists into something higher, those can contain others of themselves again. Then, we use this system to access data. The filesystem.target_drive.partition thing for instance should return something of a path maybe, ... or an access of some form.

But sometimes packages are special.

So, well - you can think of your mansion as that, ... a 3D environment. But your computer now, a convertible lends itself to that, is now like a map you hold in your hands. So, where you stand - at the beginning, your 'spawn' sotospeak, is there at the bottom left of the screen (imagine) as 'room 1', and the image goes on that we can from there branch into either room 2a or 2b. By doing so, thats the idea, you don't plot out the 3D Environment, but places that are to be there somewhere. And for the heck of it we might say that 2b be ... a portal ... that takes us to Narnia.

So, playing with portals.

So, how do we do that? Well - the software/3D stuff is still a far way away. Although, if we fancy to play around with blender, ... maybe not. At least ... somehow. What we can say is that we get to have items. So, in 3D - figuratively a bag ... like an inventory ... with stuff we 'have' within those ... things.
OK - but how? Lets not worry about that. What we have 'here' is the 'drop in'. So we can see how things get into the system. So, we want 2b to be a wardrobe. Without anything else - we can think of an empty landscape and all we have is that thing. Once placed there - it then should be a portal to somewhere. By creating stuff in the filesystem you thereby create 'space' - its so the 'archive' side of things whereby you then could go and store files ... in the VR.

But so the VR will then work specific to a set of functions or rules. And we need a specific algorithm to read the contents of a folder. So, the meaning of what is in there ... is specific to the VR then. Also. This way we can plot things out - and then later expand within it. But ... "excessive is the nature of mankind" right? ... .


Therefore, don't worry. Think about it rather in terms of files. So, lets start by saying it should be simply small. 16 gigs being excessive. 72 a porn a library. A small one ^^. Well, 128 for multimedia? Thats the problem with partitioning. If you ... get to break the limits. While else we still have 200 left in C. So, lets leave it in C. But - for the idea of ... just pimping things up a little. So, 'places' for you to work in. Thats your "excessive personal storage". In simplicity the desktop folder. "Guest Account".
And thats where you can put ... special wallpapers. "Posters". Images, "Stickers", ... that kind of stuff. Somewhere. Well - the thing isn't fleshed out yet. But ... this isn't even ... "it".

//2017.12.12|02:17