Release Notes for Qomolangma. V1.0

========================================================== ========================================================
Qomolangma openproject V1.0

Category: rich Web Client
Key words: JS Oop, JS framwork, rich Web Client, Ria, Web component,
Dom, dthml, CSS, JavaScript, JScript

Project Initiation: aimingoo (aim@263.net)
Project Team: ../qomo_team.txt
========================================================== ==========================================================

(Qomolangma openproject V1.0 architecture diagram)

I. Qomolangma 1.0 Final
======================================

Over the past year, the qomo team has been working in a state of confusion and seemingly no direction. Because qomo seems lacking
The design is necessary to explain the following to everyone who cares about it:
-What is qomo?
-Qomo

Previously, I have already said that the qomo project source is another commercial project named weui. Weui has its own complete architecture and
Direction: because the demand determines the design, in fact, the original weui design is also oriented to its original direction and needs. Me
Of course, we know the goal and direction of this requirement, but we also know that weui and qomo have similar but different directions.

Therefore, I cannot move the weui architecture to qomo or describe the qomo architecture using weui. I must
Qomo solves a problem in its preliminary work: how to turn weui into qomo.

Since an old architecture cannot serve as a new goal, we should clarify the goal and create a new architecture for it.

So, we still have the two questions above. What is the answer to qomo?

Ii. What is qomo?
======================================
For a long time, I have been emphasizing the academic aspects of qomo. However, qomo is not an academic player.
It creates a "somewhat academic taste" and aims to make him more practical. We should ensure that qomo
Can be "better practical ".

In terms of architecture, qomo has maintained its relative independence in two objectives: kernel and application. Qomo V1 will focus on
Focus on building the kernel. To enable a kernel to better meet future applications
Severe coupling exists. This allows us to reconstruct qomo (applicable to different environments) in a concise way.
Core. In qomo, this "Reconstruction" tool is a powerful Builder tool. Interestingly, this builder
It is also implemented using qomo.

Qomo is oriented to RWC (rich Web client ). In my opinion, JavaScript is a technology
But it is not a tool used only for Web pages. Many people doubt the value of this language, but I think I have already clarified
You can see the extraordinary features and energy of this language. I have also noticed that this kind of energy is available on different platforms and rings.
Environment is slowly released.

Qomo's implementation of language features is not limited to RWC. Some friends have noticed that if we just want to do something
For web pages or a set of Interface Component Libraries, we do not need to implement IOP and AOP in qomo. Qomo V1 strives to implement
These are the preparations made to release the internal energy of the Javascript language.

So:
-The qomo kernel is powerful enough to apply general extensions in different JavaScript host environments.
-Qomo is capable of providing intermediate functional requirements for bonding in different application environmentsCode.
-Qomo can be used as a part of the code package of a customized Host application to improve the application experience or local performance.

Qomo uses a general kernel layer to provide unified implementation capabilities for different host environments-a bit like. net
Or Java JVM (the role ). To achieve this purpose, qomo reflects
It also provides customized versions for special hosts through builder and kernel modularization.

The qomo application may not be an independent code body (such as a process or module), which indicates that it can be a code snippet in form or
It can be the overall solution. This feature is guaranteed by two aspects: the setting of the host by the Javascript language and
Tailored features. Therefore, you can use it to glue various modules or use it to implement applications independently.

Iii. What is the use of qomo?
======================================
Strictly speaking, qomo only implements two layers of an application (or a glued module or code snippet): the kernel layer and the application architecture layer.
The kernel layer, also known as the language layer, provides language features to give developers more programming capabilities.
Supply architecture and mechanism, such as message processing, persistence, data transmission, and parallel distribution architecture.

Qomo also has some application software for demonstration-of course, it is inappropriate to call it software strictly in meaning. Because
It may not be released or sold as software products. -- Qomo provides the purpose of these demos, which is mentioned in conjunction with Java or C #.
The purpose of the Demo code is exactly the same: let you learn how to use it.

Therefore, if you don't actually use it, qomo will "be useless ". Because it is not a product, it is not oriented to any specific
. It is a development tool and a code package or code Layer required by developers.

4. What does qomo V1 implement?
======================================
The goal and vision are great, but what real things have we done?

Qomo V1 implements the complete kernel layer. Including:
----------------
-Object-oriented systems inherited based on classes (types) are useful extensions for prototype-based JavaScript;
-Interfaces that include functions such as registration, query, and aggregation provide the capability of interface-oriented programming (IOP;
-A complete And customizable face-to-face Connection System;
-A self-managed and optional namespace system is implemented through path ing and detection;
-Scalable compatibility layer architecture;
-Enhancements to the basic JavaScript classes, including strings, arrays, and error classes;
-Public class libraries: pools, processors, time management, and time series;
-Debugging, performance analysis, compilation (connection and compression), etc.

Some application-layer code is implemented in qomo V1. Including:
----------------
-Experience version Interface Component Library, graphical component library, and Database Component Library (conceptual model, informal framework)
-Basic Framework of interface, logic, and data separation
-How to define the basic relationship between HTML description (Template) and script implementation and how to use attributes
-Qomohierarchyposter.html: used to display the namespace and class inheritance relationship in qomo (for IE only)

V. qomo V2 plan
======================================

Qomo v2 has five plans:

-Make qomo-based applications a reality. We will implement the data, interface, and basic logic framework in the qomo application layer.
The vast majority of related content, so that qomo can be applied to complex application projects.

-Enable qomo to be used for more JavaScript hosts. We will achieve better compatibility at the kernel layer to make
Qomo can be used to include acrobat script, actionscript, JScript, Rhino, and Epimetheus.
Different engines provide the same (or compatible) capabilities.

-Make qomo examples and documents more standardized and rich, and provide (or include) better testing frameworks and documentation tools.

-Allow qomo to provide cross-platform programming capabilities for different platforms. For example
.

-Better team management and project management.