Component Architecture

Everything in Omega is a component

Introduction

Omega follows the philosophy of breaking down user interfaces into components. Omega, goes one step further, and actually makes everything a component.

From text, to conditional and even dynamic directives, all are, in a sense is an omega component, just with additional data.

This also makes sense from the 'typing' point of view; to make sure the UI looks consistent, and is recognizable as OmegaUI, it is essential to have UI handle most of the part, without deviating much from the underlying language.

Implications

The reason why omega does this, is to remove the dependence of reactivity on the platform, and to the driver itself. If any operation requires some system-specific operation, like the ondestroy property depends on the platform, the driver can recognize it, and create the detectors for the specific platforms.

This, makes the code declarative, and abstracts logic that are not useful in the context of the said application.