Pype.Clicker wrote:
the '"CLI/GUI" independance seems hard to achive ... When you say "running mozilla in BASH", are you talking about launching mozilla from a shell and than have it executing in its own window or do you really believe you'll be able to translate requests for scrollbars, icons, truetype'd text and GIFs into ANSI characters ?
CLI doesn't necisarily have to be text mode graphics. There are some things one can do often faster when experianced using CLI. More than likely everything would be done atleast 640x480x16 or some vesa resolution.
That said a GUI or Hybred would be the weapon of choice for most people. However the idea is to make it as easy as possible for someone to write there own Interface be it CLI or GUI and map there comands to system calls (ex: dir, ls, or the LitheProbe File Manager click ... all same call).
Some more stuff from earlier doc:
Filesystem
The LitheFS will be a high performance journaled file system. Each LitheFS Partition will be a single partition that can be divided into parts (similar to FreeBSD). The first three values on the partition will be the preloader starting point, the preloader ending point, and the LitheFS partition table. The LitheFS Preloader is installed when the partition is created. The LitheFS Partition Table lists the different virtual partitions inside the main LitheFS partition.
The LitheFS Preloader loads the kernel, mounts the OS Partition to \OS, and loads the appropriate drivers for the kernel. After the previous steps are taken it then jumps to pmode and hands control over to the kernel which now has a filesystem and can read the configuration. The kernel then mounts other mount points and asks for user login followed by mounting the users home directory to \home.
/os This Mount point is where all they OS files reside.
/os/drivers All the drivers for the computer are located here.
/os/config This is where system configuration files are stored.
/home This is where the user?s personal files reside.
/programs This mount point may be a directory or consists of paths and/or partitions specified by the admin.
/devices This is where the currently loaded devices show.
/local Local drives and mapped network drives are mounted here.
/network This is where networks devices are listed.
LitheShell GUI (see attachment)
While LitheOS is designed to be completely shell independent an intuitive shell must still be supplied. With built-in support for drag?n?drop, favorite linking, and variable monitoring everything needed is included.
The LitheShell GUI is designed to be as fast, efficient, and user friendly as possible while loosing nothing in functionality. Due to the unique file system litheos implements the launch button actually displays the filesystem. (See illustration below)
Folders in LitheOS will be able to point to a file to launch. When a launchable folder is displayed on the menu a right click will launch while a left click will expand so the contents can be explored.
LitheProbe: Defualt Litheos File Manager
LitheTuner: Defualt Litheos Configuration Tool
Thanks,
--Jem
PS: \Kernel from previous post is actually \OS ... didn't consult my documentation.
[attachment deleted by admin]