Osiris

[thegrogen]

Another new screenshot Wow, I'm starting to churn these out almost by the hour...

[Torahteen]

Looking good. I'm working on one myself. The big difference I think is that mine is geared more toward DOS users. It's also meant to be easy to use. Bad definition. What I mean is that 90% of the actual GUI is to be made in the scripting language, RapScript.

BTW, it's called Raptor.

[thegrogen]

Cool. I'm using a similar system, as only the filemanager, controls, and I/O functions are built-in. The rest of the programs will all be executed by a bytecode interpreter, with an instruction format similar to x86 ASM. Maybe if I ever figure out the Java bytecode format, I'll use that for my bytecode format.

BTW here is another screenshot, showing off the File Manager icons and the close and minimize buttons.

[thegrogen]

Here is the start of a programmer's guide (not finished yet)

Structure of an Osiris program--------------------------------------

The structure of an Osiris program is generally quite simple. All osiris programs
are ASCII based. There will eventually be 3 languages supported, BASIC, a
modified version of ASM, and an internal bytecode. The first part of the file is
the header which will automatically be added by whatever development tools are
written in the future. This header follows the format thus:

-----------------------
Size of the program in instructions
X-Position of the program window
Y-Position of the program window
Width of the window
Height of the window
Title of the window
Icon ID
Background color (32-bit integer, you will have to do the conversion yourself)
Window flags (eg. Does the window have a border?)
Close button (whether it has one)
Minimize button (whether it has one)
Maximize button (whether it has one)
The language that the program is in
----------------------

Here is an example header:

----------------------
1
250
200
640
480
Demo Program
0
0
1
0
1
1
1
BASIC
----------------------

After this header, all program code follows. All code must have a line number
before it, even for the bytecode.

Here is a complete sample program that does nothing but loop over and over again:

----------------------
1
250
200
640
480
Demo Program
0
0
1
0
1
1
1
BASIC
10 GOTO 10
---------------------

The format described can be loaded and executed now, so all I need to do is add in commands and integrate them properly with the rest of the stuff. I'll probably write a development tool in VB.Net or FB for internal development, then port that to Osiris once all the commands are supported.

[marzecTM]

if i was in your place i'd rather write a small script language rather than hardcoding "commands". having variables and the like introduced in a script language is really easy. a proper lexer and parser aren't big problems either and you can have interpretation for free if you construct an ast.

[thegrogen]

It IS a scripting language. It the programs are not hardcoded, and I am writing a parser for the various scripting languages I plan on supporting. I'll probably implement a Python interpreter at some point.

[thegrogen]

I changed the colour scheme:


Do you think it looks better than the old scheme? Please let me know.

[Kylemc]

I prefer the other one. Make it so that the user can customise the appearance.

[Kevin_theprogrammer]

Yeah, a control panel with a theme manager option...
Another good idea would be to allow an incorporation of DLLs so the shell is easily extendable...and if you want it to be somewhat like a true OS, you make a SCSI disk image and store all your files in there by means of a FS other than FAT(if using win9x), NTFS(if using 2k/XP), or ext3(if using linux)... Doing this can lead it 1 step closer to an OS...

[speedlemon]

colors are fine. the name sucks imo. :roll: