• View
• Edit
• History
• Print

Components

Author: Telcontar
See also: Cy/VOS structure and components

This section refers to non-core software packages and components that can be used to provide non-core services or enhance the system. Some of these will ship as standard with some distributions, but are not required for the system to function in any way. "Non-core" in this context refers to components and services that are not required for the operating system to run, but may be required to drive common parts of the standard modern computing interface. For a list of required, built-in components see Cy/VOS structure and components.

Contents

• Processes
• Modules

Processes

The following are fully-fledged, stand-alone processes.

Process classes

• System manager - A centralised area for managing the computer
• Installation manager - A class of programs used to manage process installation
• Configuration editor - A class of programs used to manage system configuration
• Low-level window manager - Used to underpin and drive the GUI
• Task manager - A class of programs used to view and manage running processes
• Desktop - A class of programs used to view the desktop
• Status and utility widgets
• Emergency User Interface - A fallback UI in case the main interface fails

Applications

• Window Toolkit Server? - Widget set and window content provider
• The MicroGUI - A lightweight user window environment
• EventsArea - A user notification manager
• Audio Server - Low level global audio server, provides wave-mixing
• Session Sound Server - Asynchronous audio server
• Shell UI Server - Rudimentary GUI support to scripts

The windowing environment will probably have to be listed here, but seeing as LayerGUI is layered, and there are ideas about universal interface (semantic split core/UI interaction) it remains hard to define at present which parts of the interface environment will be in core. Something to service a basic full-screen console will be needed, and graphical booting (software fonts and scrolling, progress bars, etc) will be provided by the minimal NanoGUI in the bootloader in some builds. Server-only (UI-free) builds may survive like this but console builds will probably at least need the text side of the universal interface service even if the graphical side is not present.

Modules

The following are global plug-in modules designed to support the system

• Graphical file system navigation
• Global contextual menu item providers
• File format support
  • Audio read and write (see AudioServer)
  • Image read and write
  • Video read and write
• Text rendering
• Text input

Also

Support software lists some more -- these two pages may need to be merged at some point!