A new storage layer is currently in development for TriangleOS, the VFDBS, which aims at replacing the VFS in order to change the way data is stored and handled through the entire OS (all data is centralised, support for meta-data, journaling for all filesystems, etc.). The User Interface also needs to change to enable the user to quickly browse through all the information.
http://www.wcools.nl/screenshots/004_appl.PNG
Can’t keep a good OS design down, I see.
damn right!
*sigh*
That was pre 0.0.5.
As much as I love BeOS, the yellow tabs were horrible. As you can see, it wasn’t as good as some think. ; ) http://www.wcools.nl/screenshots/gui005_screenshot.PNG
double blast! The tabs were NOT horrible. How anyone can think that is beyond me.
/me cuddles his slidy, yellow tabs
this project is still alive?!
and trudging along at a glacial pace, since one person (Wim) is solely responsible for it’s development. I suspect that he has other thing in his life that take up his time, hence why it takes so long between version updates.
Luposian
What a lot of these hobby operating systems lack is good documentation, some do have documentation but rarely can you read the first five or ten pages and already be on your way to writing and compiling a program with the language of your choice.
I remember when Seal (the DOS gui) was still alive, I really wanted to learn how to write applications for it but there just wasn’t current or even half complete documentation for it and it was all for C. Good documentation, preferably with documentation for both people who want to take their time and people who want to start working quickly, would help out some of these projects.
An OS in Assembly language, Cool concept can’t beat that in speed.
Just because it was written in ASM doesnt mean its fast, the authors must use proper coding practice also.
Is anyone but me wondering why did Eugenia post a news about Some Guy’s uninnovative, closed, slowly developed own OS incompatible with anything, a project without any future? – ..well, except because it is an *OS*.
Personally I think reading it was a wasted time..
Firstly, in regards to TriangleOS:
The size of the OS alone is impressive, especially considering what is given. The application is very quick, as expected and very intuitive. On the site, in regards to the screenshots and the pdf for vfdbs, I am enamored with the new storage layer planned.
It is upsetting realizing that there is only one person working on the OS, and that it will be a long time for any updates, but this (as most) is a hobby OS, and that is what is expected. I love the concept and the design, I have actually decided to use this style in my system.
Adastra:
Of course there probably are people out there wondering the same thing, though i’m also positive of the fact that not only are they close-minded, like you, they also comment on topics they didn’t take the time to read, like you.
Let’s break it down adastra style.
[code]
#!/usr/bin/pike/pike
inherit “comprehend.pike”
void main() {
object ob;
ob=compile(“new_os”);
if( !(adastra_decipher(arg)) )
werror(“Can’t comprehend!
“);
else
werror(“Wow. That’s neat!
“);
}
private int adastra(object arg) {
if(!opensource(arg) && !myfavlicense(arg) && iwannalookcoolagainst(arg) || ithinkimcooltoday(time()))
return 0;
else
return 1;
}
[/code] <–(I know they don’t work, it’s for emphasis)