Framework and Compatibility

The AppStudio component directory follows the principles of modular and layered design to ensure that the component system is scalable, maintainable, and highly reusable. The overall directory structure is as follows:

.
├── as-button.js
├── ... ...
├── index.js
├── basic/
├── fp-ext/
├── services/
└── utils/

1. services/

This directory contains the core runtime support services for components, such as task scheduling and processing logic.

• processing-queue.js Provides task handling for rendering and interaction, ensuring ordered and efficient operations throughout the component lifecycle.

2. basic/

The foundation layer of the component system, defining shared behaviors and core abstractions for all components.

• as-event.js — Defines inter-component communication with a unified event registration, dispatching, and listening interface.
• as-base.js — Establishes component structure and construction conventions; serves as the base class for all components.
• as-accessors.js — Abstracts unified methods for accessing and mutating component properties to ensure consistency.
• as-component.js — Defines rendering and update rules to enable reusable rendering logic across components.
• as-container.js — Provides core dependencies and rendering logic for container-type components.
• as-view.js — Offers common dependencies for view-type components, implementing a unified rendering pattern for UI views.

3. fp-ext/

The functional extension layer for OmniCore App SDK components. It enables enhanced functionality and custom behavior based on business needs while maintaining full SDK compatibility.

This layer allows for differentiated logic extensions without disrupting the underlying component architecture.

4. utils/

Contains shared utility methods supporting logic reuse and general computation across components.

• utils.js — Typically includes helpers for type checking, data transformation, and event encapsulation.

AppStudio evolves continuously, and updates to the framework may introduce breaking changes in the following internal directories:

• basic/
• utils/
• services/
• fp-ext/

While these internal modules provide essential functionality, backward compatibility is not guaranteed between framework versions.

However, the TComponent interface remains fully stable and backward-compatible. Therefore, it is strongly recommended that developers rely on the TComponent-level APIs for integration or extension, and monitor framework version changes carefully when directly invoking lower-level functions from these internal modules.