The major design goal of Synergy OS is to be a highly flexible and customizable suite of software components forming a real Web OS on top of any operating system. For the first step, Synergy OS it will be compatible to some standard Linux distributions.

In Synergy OS, Apps are written in Javascript (EcmaScript) and are executed by the high-performance javascript VM “V8″. V8 comes from Chrome OS. Apps are using the Synergy OS foundation classes to get access to the resources of the real operating system they are executed on. So Apps have no direct dependency to the real OS.

The foundation classes of Synergy OS are well designed and well namespaced. They are grouped in:

• The “Synergy OS Framework”
• The “Synergy Web Framework”

Because WebApps in Synergy OS are executed in a locally webbrowser, there is a client side of an App and a server side of an App. It is also possible to write LocalApp’s. These run in the shell and have no webbrowser based client code.

The foundation classes for the Web contain classes for GUI rendering, Video control, Audio control, Network communication and Input event handling in the webbrowser.

The foundation classes for the Core contain classes for controlling system services and devices (hardware management) and all features a cutting edge web framework needs to be amazing. Plans are there to implement all features of Zend Framework and Ruby on Rails.

The architecture in detail

The anatomy of Synergy OS is a component orientated architecture. The foundation classes wrap the functionallities of the components.

The whole foundation classes are defined by an WebIDL specification (see W3C Web IDL for more informations). Web IDL is a language independend interface definiton language. We plan to integrate an extended version of the WebIDL compiler from the ES Operating System into Synergy OS.

The foundation classes of the Core are implemented in Java on basis of OpenJDK. The backend of a WebApp or a LocalApp in general is implemented in Javascript. So how is Javascript calling the Java libraries?

This is simple. We will patch V8 to have direct binding to Java compiled libraries by using the Java Native Interface wrappers (they are also used in SWT (Eclipse), QTJambi etc.).

The classes of the Synergy OS Framework abstract the functionalities of the real operating systems. They will be designed in a component orientated manner.

What about compatibility?

Each Linux distribution has it’s own design decisions in mind. Specially for target devices, performance optimization etc. So for example X.org is used in conjunction with some desktop environment like Gnome or KDE in most of the distributions. How can Synergy OS be compatible to these distributions if Synergy OS comes with it’s own special SynergyView GUI?

The answer is quite easy. We just change the boot process of a target distribution when installing Synergy OS on top of it. This means that after installing Synergy OS on your linux box, the desktop environment of your Xorg configuration will be replaced by starting the SynergyView instead. The SynergyView is also based on X btw. – for Windows SynergyView runs native on the Windows desktop. It even runs on BSD systems.

It is the same for any other overlay. For example the standard shell will be replaced by the Synergy (the EcmaScript shell) which is able to interpret javascript on console etc.

In general, a linux distribution or in the future any other OS is nothing more or less than just a Synergy OS backend target. We customize the install process of Synergy OS for every backend OS and need to write the foundation classes backends for missing components support but thats all. Even the foundation classes (e.g. the Synergy OS Framework) must not be ported. It’s Java.

Does that mean Synergy OS fit’s into different design goals automatically?

Yes. It sounds crazy – but this an effect of Synergy OS’s meta design. If you want Synergy OS to run perfectly on your Mobile Phone or Netbook, you can just install Synergy OS on a linux distribution customized for mobile (For sure there need to be a Synergy OS backend for this OS/distro). Normally it just overlays the GUI, the standard UI, some things in the boot process etc. to be able to run all Synergy OS apps smoothly.

Synergy OS does for example not touch the Xorg configuration. So special settings for mobile distributions would not be affected and the SynergyView just applies to the special requirements of that mobile distribution. Same for power magement, audio, hardware accelleration etc.

From an application developers point of view this means

As an application developer you can write one application that runs on any operating system supported as a backend of Synergy OS. The number of supported OS’s will grow fast because there is more or less nothing to do to port Synergy OS to different distributions or even to BSD.

For an application developer there is also no magic in writing cool new applications for Synergy OS. There are two types of Apps that can be written for Synergy OS in general:

• LocalApps
• WebApps

A LocalApp runs locally without any SynergyView (Web GUI). It can be implemented in Javascript or Java. But you will choose Javascript normally. It has full access to the Synergy OS Framework. Console programs, system services and other scripts etc. should be implemented as LocalApp.

A WebApp is a zipped application bundle that is splitted into it’s frontend and backend part. There is code which needs to be executed in the SynergyView environment and code that needs to be executed in the webserver backend. So a WebApp bunde contains “frontend”, “backend” and “resources” directories. It is packed as zip file just for easier singning, installing and deployment reasons. A WebApp can only be written in Javascript (maybe we write some kind of cross-compiler like GWT in the future). The backend of a WebApp can be written in Java too but this is not recommended.

So if you have some experience in web application development or just in scripting ActionScript, Javascript, JScript or one of the hundreds of other EcmaScript based languages there is more or less no learn for you. You can directly start wirting amazing Apps for Synergy OS.

The future goal

Synergy OS must not be regressed to support Linux as backend OS. Why not implementing Synergy OS foundation classes and component backends for BSD, Windows and Mac?

The Synergy OS Framework is written in Java, the EcmaScript VM is V8 and already ported to any modern OS. So there is not much todo to port Synergy OS to any other modern real operating system.