Android core analysis-Basic Principles of Android GWES

 

Android GWES framework

 

The term GWES here is actually transplanted from Microsoft's Window. GWES is used to indicate that the Android Window Event System is not so accurate. In Android, Window is a relaxed concept, it is more manifested in the concept of View. To a large extent, the concept of View in Android can replace Microsoft Window. It is a bit more difficult than Microsof. I don't need the concepts you have used, this is what I think the designer intends to do.

 

Basic Framework of the original GUI

 

First, we start from the feature space outside the Android SDK. When compiling Actvitiy, we all face the processing function: OnXXXX (), for example, pressing a key or OnKeyDown, in this process, what does the system do? To understand this process in detail, we need to understand Andoid's View Management, window system, message system, and input system. We start from the most fundamental point. As an embedded graphical user interface system, Android has the same basic principle as general GUI, it also follows the general rules of GWES (Graphic window Event System). In general, Android is a system that manages user input and system screen output. In fact, the name GWES is more representative of the basic elements of the GUI: graphics, windows, events.

1. Basic Components of General GUI

The implementation of GUI is to manage the three basic elements mentioned above. According to the features and scope of these three elements, GUI can be divided into three parts:

• Event manager
• Window Manager
• GDI (drawing and GDI logical Object Management)

 

(1) event manager

• Collect system messages, convert and distribute system messages and user messages to window objects.
• Message Queue Management

(2) Window Manager:

• Create and destroy a Management window
• Drawing a window
• Activity window, switch of input focus
• Window Relationship Management
• Control, menu implementation

(3) GDI

• Context device management
• Context device object management: fonts, brushes, etc.
• Drawing: point, line, fill, etc.
• Image operations: Bit transfer and bitmap operations

2 system architecture and general trend of Data Flow

 

 

 

 

In essence, GUI is used to manage user input and screen output. From the above architecture, we can see the basic flow of the two GUI data streams, which also determines the most basic focus of Android GWES design.

Android weakens the concept of window and focuses on the concept of View. Therefore, the basic components of Android can be modified from the preceding figure to the following components:

 

Android GWES framework

 

The term GWES here is actually transplanted from Microsoft's Window. GWES is used to indicate that the Android Window Event System is not so accurate. In Android, Window is a relaxed concept, it is more manifested in the concept of View. To a large extent, the concept of View in Android can replace Microsoft Window. It is a bit more difficult than Microsof. I don't need the concepts you have used, this is what I think the designer intends to do.

 

Basic Framework of the original GUI

 

First, we start from the feature space outside the android SDK. When compiling actvitiy, we all face the processing function: onxxxx (), for example, pressing a key or onkeydown, in this process, what does the system do? To understand this process in detail, we need to understand andoid's View Management, window system, message system, and input system. We start from the most fundamental point. As an embedded graphical user interface system, Android has the same basic principle as general GUI, it also follows the general rules of GWES (Graphic window Event System). In general, Android is a system that manages user input and system screen output. In fact, the name GWES is more representative of the basic elements of the GUI: graphics, windows, events.

1. Basic Components of General GUI

The implementation of GUI is to manage the three basic elements mentioned above. According to the features and scope of these three elements, GUI can be divided into three parts:

• Event manager
• Window Manager
• GDI (drawing and GDI logical Object Management)

 

(1) event manager

• Collect system messages, convert and distribute system messages and user messages to window objects.
• Message Queue Management

(2) Window Manager:

• Create and destroy a Management window
• Drawing a window
• Activity window, switch of input focus
• Window Relationship Management
• Control, menu implementation

(3) GDI

• Context device management
• Context device object management: fonts, brushes, etc.
• Drawing: point, line, fill, etc.
• Image operations: Bit transfer and bitmap operations

2 system architecture and general trend of Data Flow

 

 

 

 

In essence, GUI is used to manage user input and screen output. From the above architecture, we can see the basic flow of the two GUI data streams, which also determines the most basic focus of Android GWES design.

Android weakens the concept of window and focuses on the concept of view. Therefore, the basic components of android can be modified from the preceding figure to the following components: